64 skills (repositories by tt-a1i) · sorted by popularity
Evaluate slow, unreliable, duplicated, or brittle tests by the behavior they protect and their maintenance cost. Use it to choose focused checks, justify additions or removals, and distinguish product bugs from outdated expectations or environment failures.
Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.
Evaluate improvements to Archify diagrams using actual outputs and agent work records. Compare accuracy, readability, and total delivery time to investigate layout, connection routing, diagnostics, and authoring guidance, then document what the evidence supports.
Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.
Turn plain-language descriptions, Mermaid diagrams, or repository evidence into interactive standalone HTML diagrams. Create system maps, workflows, timelines, database relationships, and everyday process diagrams, with automated validation, light and dark themes, and image, SVG, or WebM export.
Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.
The English summary is being prepared. Showing the original description.
Implement the result of /to-spec and /to-tickets in code.
The English summary is being prepared. Showing the original description.
Conduct a retrospective on a coding session.
The English summary is being prepared. Showing the original description.
Use when writing a PR body.
The English summary is being prepared. Showing the original description.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
The English summary is being prepared. Showing the original description.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
The English summary is being prepared. Showing the original description.
Execute approved, bounded work in an isolated implementation conversation and return a structured evidence receipt. Use with inherited history or an explicitly identified source; no particular planning, testing, or review skill is required.
The English summary is being prepared. Showing the original description.
Scan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.
The English summary is being prepared. Showing the original description.
Ask which skill or flow fits your situation. A router over the skills in this repo.
The English summary is being prepared. Showing the original description.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
The English summary is being prepared. Showing the original description.
Writing, exploit: shape raw material into an article, paragraph by paragraph.
The English summary is being prepared. Showing the original description.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
The English summary is being prepared. Showing the original description.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design.
The English summary is being prepared. Showing the original description.
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
The English summary is being prepared. Showing the original description.
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
The English summary is being prepared. Showing the original description.
Compact the current conversation into a portable handoff document, with an optional live clarification path for compatible Codex tasks.
The English summary is being prepared. Showing the original description.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
The English summary is being prepared. Showing the original description.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
The English summary is being prepared. Showing the original description.