sync-docs
Update and maintain project documentation for CLAUDE.md and README.md:
1. CLAUDE.md Management
Purpose: Keep Claude's project instructions current and accurate
- Scan project structure: Check for new tools, scripts, build systems
- Update build commands: Sync with package.json, Makefile, or build configs
- Add new patterns: Document coding conventions, file organization
- Refresh tool commands: Update linting, testing, deployment instructions
- Check environment setup: Verify installation and setup steps
2. README.md Maintenance
Purpose: Keep public project documentation up-to-date
- Update installation: Check dependencies, requirements, setup steps
- Refresh usage examples: Verify code samples and API documentation
- Validate links: Test external links, badges, and references
- Update project status: Current features, roadmap, version info
- Check screenshots/demos: Ensure visual examples are current
More from tartinerlabs/skills
project-structure
Use when deciding where code should live, organising files, or auditing project structure. Checks colocation, grouping, and directory anti-patterns.
182tailwind
Use when writing Tailwind classes, fixing spacing issues, reviewing CSS, or auditing Tailwind patterns. Enforces v4 best practices for grid and responsive.
156security
Use when auditing security, checking for vulnerabilities, scanning for secrets, or reviewing dependencies. OWASP Top 10 audit with GitLeaks and dependency checks.
152refactor
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits TS/JS for dead code, nesting, and patterns.
152commit
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional commit format and GitLeaks scanning.
147create-branch
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
143