gw Configuration Management
Configure gw-tools for optimal workflows across different project types and team environments.
Rules
| Rule | Description |
|---|
| fundamentals | HIGH - Config file location, creation, and precedence |
| options-reference | HIGH - Complete reference for all config options |
| setup | HIGH - Initial setup flow, secrets, team onboarding |
| auto-copy | HIGH - File patterns to copy, what to include/exclude |
| team-config | MEDIUM - Sharing config, documentation, onboarding |
| advanced | LOW - Multiple sources, secret management integration |
| troubleshooting | HIGH - Common issues and solutions |
Project-Type Patterns
| Pattern | Description |
|---|
| nextjs | MEDIUM - Next.js with Vercel deployment |
| nodejs-api | MEDIUM - Node.js backend/API services |
| monorepo | MEDIUM - pnpm/Yarn/npm workspaces |
| react-spa | MEDIUM - React Single Page Applications |
Quick Reference
| Task | Command |
|---|
| Initialize config | gw init |
| Initialize with options | gw init --auto-copy-files .env,secrets/ |
| Interactive setup | gw init --interactive |
| Clone and initialize | gw init git@github.com:user/repo.git |
| Sync files to worktree | gw sync feature-branch |
| Show setup command | gw show-init |
Configuration Options
| Option | Purpose | Default |
|---|
root | Repository root path | Auto-detected |
defaultBranch | Source for file copying | "main" |
autoCopyFiles | Files to auto-copy | [] |
updateStrategy | merge or rebase | "merge" |
cleanThreshold | Days before stale | 7 |
autoClean | Prompt for cleanup | false |
Key Principles
- Set up secrets in defaultBranch first: Source must exist before auto-copy works.
- Commit config to version control: Team gets it automatically.
- Copy secrets, not dependencies:
.env yes, node_modules no.
- Use
gw show-init for documentation: Generate setup command.
Related Skills
Resources