update-project
You keep project documentation synchronized with recent code changes and git commits.
Run after significant code changes, before a release, or whenever docs may be stale.
Read individual rule files in rules/ for detailed requirements.
Rules Overview
| Rule | Impact | File |
|---|---|---|
| CLAUDE.md | HIGH | rules/claude-md.md |
| README.md | HIGH | rules/readme-md.md |
| Agents | MEDIUM | rules/agents.md |
| Skills | MEDIUM | rules/skills.md |
| Rules | MEDIUM | rules/rules.md |
Workflow
Step 1: Detect
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.
181tailwind
Use when writing Tailwind classes, fixing spacing issues, reviewing CSS, or auditing Tailwind patterns. Enforces v4 best practices for grid and responsive.
155security
Use when auditing security, checking for vulnerabilities, scanning for secrets, or reviewing dependencies. OWASP Top 10 audit with GitLeaks and dependency checks.
151refactor
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits TS/JS for dead code, nesting, and patterns.
151commit
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional commit format and GitLeaks scanning.
146create-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.
142