Claude Skills by me-cedric

Use when creating or updating a Spec Kit project constitution, governance rules, principles, or non-negotiable constraints.

Use after implementation to reconcile Spec Kit artifacts, code, tests, docs, and implementation status.

Use when executing approved Spec Kit tasks after spec, plan, tasks, and checklists are ready.

Use when creating a Spec Kit technical plan, research notes, data model, contracts, quickstart, or validation plan from an approved spec.

Use when running a Spec Kit specify step to create or update a feature specification from a natural-language feature request.

Use when generating Spec Kit implementation tasks from an approved plan and design artifacts.

Use when converting Spec Kit tasks.md items into deduplicated GitHub issues tied to the current repository.

Split delivery work across the project's personas (profiles) and write the assignment plan as validated JSON. Use when the user asks who does what, to dispatch or assign tasks, to split work by profile or role, to build a work-breakdown per developer, or to produce an assignment brief per team member.

Change verification gate. Analyzes code changes, checks documentation sync, and assesses change impact. Use when the user mentions change checks, doc sync, code review, pre-commit checks, or diff analysis. Auto-triggers for design-level changes and completed refactors.

Module completeness gate. Scans the directory structure, detects missing documentation, and verifies code/doc sync. Use when the user mentions module verification, doc checks, structural completeness, README checks, or DESIGN checks. Auto-triggers when a new module is completed.

Code quality gate. Detects complexity, duplicated code, naming-convention violations, function length, and other quality metrics. Use when the user mentions code quality, complexity checks, code smells, refactoring suggestions, lint checks, or coding standards. Auto-triggers for complex modules and completed refactors.

Security verification gate. Scans code for vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when the user mentions security scans, vulnerability detection, security audits, code security, OWASP, injection detection, or sensitive-data leaks. Auto-triggers for new modules, security-related changes, offensive/defensive tasks, and completed refactors.

Prove that a built screen matches its reference — a Figma export, a generated HTML preview, or a mockup image — with deterministic Playwright screenshots. Use when the user asks for visual regression, screenshot tests, pixel diffs, "does the build match the design", or when you change any user interface and must ship visual proof instead of a claim.

Split a backlog of work-items across people or agents with clear separation of concern, minimal file overlap, explicit coordination seams, and a shareable assignment brief per owner. Use when dividing work across a team, deciding who does what, or parallelizing work so contributors don't collide.

Use when the user asks to change how you communicate or how much you build — be terse, use fewer tokens, caveman mode, stop over-engineering, be lazy, YAGNI, simplest solution, action-first output, no preamble, or rewrite text so another agent cannot misread it. Installs the tracked style skill that matches the request and applies the compass precedence rules when several are active. Triggers: caveman, ponytail, i-have-adhd, asd-ste100, be brief, less tokens, terse, minimal solution, do less,...