Loading...
Loading...
Found 6,822 Skills
Use when symfony doctrine transactions
Reconcile the project's FPF state with recent repository changes
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Use when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that outlives its author. Triggers - 'documentation gate', 'decision record', 'ADR', 'acceptance report', 'runbook', 'is this verified', 'доказательная документация', 'записать решение', 'отчёт о приёмке', 'раннбук', 'чем это подтверждено', 'доки в синхроне'. Not for: drafts, chat answers, commit messages or code comments — say 'без доков' to opt out.
Design evidence-led before-and-after short-form ads from product facts, approved proof, reference analysis, or rough concepts. Use for before/after ads, transformation ads, problem-solution-result UGC, skincare/body/wellness routines, visual comparison scripts, or approved before-after scripts that should proceed to image-batch-runner or video-batch-runner.
Evidence-first design review of a PR's UI. Walks the changed screens in a real browser, performs the user's tasks, and posts findings ranked by user impact, each with evidence, a pattern, a trade-off and an acceptance criterion.
One-time project setup for creative writing. Interviews you about your project, collects writing samples, proposes kb structure, and creates CLAUDE.md with project conventions.
Debug Rails issues systematically. Use when encountering ActiveRecord errors like RecordNotFound, routing issues, N+1 query problems detected by Bullet, asset pipeline issues, migration failures, gem conflicts, ActionController errors, CSRF token problems, or any Ruby on Rails application errors requiring diagnosis.
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.
Technical Design - picks one variant per problem area from the research catalogue, then produces architecture diagrams, interfaces, and data flow. Decisions live here, not in research.
Write a developer value proposition that is specific, provable, and free of puffery. Use when the messaging leans on "powerful," "better," "seamless," or "best-in-class," when claims have no proof, or when the same line is supposed to reach both the developer and the buyer.
Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.