refactor-agents
Refactor existing AGENTS.md to follow progressive disclosure principles
What this skill does
# Refactor AGENTS.md
Optimize an existing AGENTS.md file using progressive disclosure principles. Extracts essentials to root, groups related instructions into sub-files, and flags content for deletion.
## Step 1: Load Current State
```
AGENTS_FILES = Glob("**/AGENTS.md")
ROOT_AGENTS = Read("AGENTS.md")
```
If no AGENTS.md exists: suggest `Skill("init")` instead.
## Step 2: Find Contradictions
Analyze ROOT_AGENTS for conflicting instructions:
| Contradiction Type | Example |
|-------------------|---------|
| Version conflicts | "Use Node 18" vs "Requires Node 20" |
| Style conflicts | "Use tabs" vs "2-space indent" |
| Tool conflicts | "Use npm" vs "pnpm install" |
| Process conflicts | "Always write tests first" vs "Tests optional for prototypes" |
For each contradiction found:
```
AskUserQuestion:
question: "Found conflicting instructions: [A] vs [B]. Which should we keep?"
options: [A, B, "Keep both with context", "Remove both"]
```
## Step 3: Identify Essentials
Extract ONLY content that belongs in root AGENTS.md:
| Keep in Root | Move to Sub-file |
|--------------|------------------|
| One-sentence project description | Detailed architecture docs |
| Package manager (if not npm) | Framework-specific patterns |
| Non-standard build/test commands | Testing conventions |
| Universal security rules | Component-specific rules |
| Links to sub-files | Verbose examples |
**Root target:** 60-100 lines (max 200)
## Step 4: Group Remaining Content
Categorize instructions into logical groups:
| Category | Typical Content |
|----------|-----------------|
| `conventions/typescript.md` | TS strict mode, type patterns, import style |
| `conventions/testing.md` | Test structure, mocking rules, coverage |
| `conventions/git.md` | Branch naming, commit format, PR process |
| `conventions/api.md` | Endpoint patterns, error handling, auth |
| `conventions/styling.md` | CSS approach, component styling, themes |
For ambiguous content:
```
AskUserQuestion:
question: "Where should '[instruction]' live?"
options: [category suggestions based on content]
```
## Step 5: Flag for Deletion
Identify instructions that should be removed:
| Flag | Reason | Example |
|------|--------|---------|
| REDUNDANT | Agent already knows | "Use meaningful variable names" |
| VAGUE | Not actionable | "Write clean code" |
| OBVIOUS | No new information | "Test your changes" |
| OUTDATED | No longer applies | References deprecated tools |
| DUPLICATE | Already stated elsewhere | Same rule in multiple places |
Present flagged items for confirmation:
```
AskUserQuestion:
question: "These instructions seem [redundant/vague/obvious]. Delete them?"
options: ["Delete all", "Review each", "Keep all"]
```
## Step 6: Generate New Structure
Create the refactored file structure:
```
AGENTS.md # Minimal root (60-100 lines)
.agents/ # Sub-files directory
conventions/
typescript.md
testing.md
git.md
patterns/
[domain-specific].md
```
### Root AGENTS.md Template
```markdown
# [Project Name]
[One sentence description]
## Quick Reference
- **Stack:** [tech stack summary]
- **Build:** `[build command]`
- **Test:** `[test command]`
- **Lint:** `[lint command]`
## Conventions
See detailed guides in `.agents/conventions/`:
- [TypeScript](.agents/conventions/typescript.md)
- [Testing](.agents/conventions/testing.md)
- [Git Workflow](.agents/conventions/git.md)
## Security
- Never commit secrets or `.env` files
- [Other universal security rules]
## Before PR
\`\`\`bash
[single command that runs all checks]
\`\`\`
```
## Step 7: Write Files
1. Backup original: `mv AGENTS.md AGENTS.md.backup`
2. Write new root AGENTS.md
3. Create `.agents/` directory structure
4. Write each sub-file
## Step 8: Verify
Report refactoring results:
```
## Refactoring Complete
### Before
- Root AGENTS.md: [X] lines
- Sub-files: [Y]
### After
- Root AGENTS.md: [X] lines (target: 60-100)
- Sub-files: [list with line counts]
### Changes
- Contradictions resolved: [count]
- Instructions moved: [count]
- Instructions deleted: [count]
- Redundant: [count]
- Vague: [count]
- Obvious: [count]
### Backup
Original saved to: AGENTS.md.backup
```
## Error Handling
| Condition | Action |
|-----------|--------|
| No AGENTS.md found | Suggest `Skill("init")` |
| Already minimal (<100 lines) | Ask if optimization still wanted |
| No contradictions found | Skip to Step 3 |
| User cancels at any step | Preserve original, no changes |
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.