home / skills / d-oit / do-novelist-ai / tech-stack-specialist

tech-stack-specialist skill

safe

This skill helps you manage frameworks, dependencies, and build configurations to stabilize projects and accelerate development.

npx playbooks add skill d-oit/do-novelist-ai --skill tech-stack-specialist

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.6 KB

---
name: tech-stack-specialist
description:
  Manage framework usage, dependencies, build configuration, and environment
  setup. Use when adding new dependencies, updating packages, configuring build
  tools, or setting up development environment.
---

# Tech Stack Specialist

Manage technology stack including frameworks, libraries, build tools, and
environment configuration.

## Quick Reference

- **[Framework Usage](framework-usage.md)** - React, TypeScript, Vite patterns
- **[Dependency Management](dependency-management.md)** - NPM, pnpm, dependency
  updates
- **[Build Configuration](build-configuration.md)** - Vite, Rollup, build
  optimization
- **[Environment Setup](environment-setup.md)** - Environment variables, config
  files

## When to Use

- Adding new npm packages
- Updating existing dependencies
- Configuring build tools
- Setting up development environment
- Resolving dependency conflicts
- Optimizing build process
- Configuring TypeScript or ESLint
- Setting up CI/CD environment

## Core Methodology

Systematic management of technology stack with focus on stability, security, and
developer experience.

**Key Principles**:

1. Use pnpm for fast, reliable installs
2. Keep dependencies up to date
3. Use exact versions where critical
4. Configure proper TypeScript strict mode
5. Set up environment validation
6. Separate dev/prod dependencies appropriately
7. Use environment variables for secrets
8. Document breaking changes

## Integration

- **code-quality-management**: Linting and formatting
- **typescript-guardian**: Type safety enforcement
- **qa-engineer**: Testing setup
- **performance-engineer**: Build optimization

## Best Practices

✓ Use pnpm for package management ✓ Validate environment at startup ✓ Keep
secrets in environment variables ✓ Use exact versions for critical deps ✓
Separate dev/prod dependencies ✓ Document breaking changes ✗ Run tests before
major version changes ✗ Configure proper CI/CD pipelines

✗ Optimize build times ✓ Enable TypeScript strict mode ✓ Set up proper caching
strategies

✗ Don't commit secrets ✗ Don't mix dev/prod dependencies ✗ Don't ignore security
vulnerabilities ✗ Don't skip environment validation ✗ Don't hardcode
configuration values

---

## Content Modules

See detailed modules:

- **[Framework Usage](framework-usage.md)** - React, TypeScript, Vite
- **[Dependency Management](dependency-management.md)** - NPM, pnpm, updates
- **[Build Configuration](build-configuration.md)** - Vite, Rollup
- **[Environment Setup](environment-setup.md)** - Environment config

Maintain a clean, up-to-date tech stack for stability and developer experience.

Overview

This skill helps teams manage frameworks, dependencies, build configuration, and development environment setup to keep projects stable, secure, and fast to iterate on. It provides practical guidance for adding or updating packages, configuring TypeScript and build tools, validating environment variables, and separating dev/prod concerns. The goal is reliable builds, predictable installs, and a better developer experience.

How this skill works

The skill inspects package manifests, lockfiles, and build configs to recommend package manager strategies, version pinning, and dependency separation. It suggests TypeScript, linter, and build tool settings, enforces environment validation patterns, and proposes caching and CI adjustments to speed builds. When given a change request, it recommends exact steps and configuration edits to implement safely.

When to use it

Adding or removing npm/pnpm packages
Updating or pinning dependency versions
Configuring or migrating build tools (Vite, Rollup)
Setting up or validating development and CI environments
Resolving dependency conflicts or security issues

Best practices

Use pnpm for deterministic, fast installs and smaller node_modules
Pin exact versions for critical dependencies and document breaking changes
Enable TypeScript strict mode and keep lints enforced in CI
Separate devDependencies from production dependencies
Validate environment variables at startup and keep secrets out of the repo

Example use cases

Add a new UI library and update build config to ensure tree-shaking and code-splitting
Migrate from npm to pnpm and update CI caching for faster installs
Resolve a dependency conflict by hoisting or pinning transitive versions
Enable TypeScript strict mode and fix resulting type errors incrementally
Add environment validation and fallback warnings to prevent misconfigured deployments

FAQ

Should I always use pnpm?

pnpm is recommended for speed and storage efficiency, but choose the manager that fits team constraints and CI support. Consistency across developers and CI is most important.

When should I pin exact versions?

Pin exact versions for critical runtime dependencies and libraries with breaking changes. For less critical packages, use caret ranges with regular update checks and automated testing.