Loading...
Loading...
Found 184 Skills
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Specializes in generating Action-Domain-Responder (ADR) boilerplate for Gravito projects. Trigger this when adding new features or modules using the ADR pattern.
Create, update, or supersede architecture decision records under `architecture-decisions/`. Use when the user asks for ADR work or `spec-loop-plan-task` routes ADR writing.
Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.
Clarify or discuss a proposed task, plan, design update, or ADR by resolving the highest-value unresolved decisions, decision criteria, trade-offs, and option boundaries until the inputs are ready for task creation, task planning, task/design updates, ADR writing, or safe implementation continuation. Use this as the default path when the user asks to clarify, discuss criteria, compare options, stress-test a design, or otherwise resolve material unresolved questions before proceeding. When clarification ends, resume the invoking workflow. It may also be used for general grilling when explicitly selected or when no other default grilling skill is available.
Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision. Follows the standard ADR format with context, decision, and consequences. Invoked when the user says "write an ADR", "document this decision", or "create an architecture record".
Use this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Use when writing ADRs, recording decisions, or evaluating options.
Create, update, review, and reference architecture decision records (ADRs) in the current git repository. Use when the user asks messy design questions, wants a design doc turned into ADR draft(s), needs existing decisions checked before implementation, wants gaps surfaced before writing an ADR, or wants future sessions to reuse decisions consistently. Inspect repository code and docs first, ask only for missing decision-critical information, then produce or update ADR files using the repo’s ADR conventions or the defaults in references/.
Helps engineering managers break down knowledge silos and build sustainable documentation and collaboration practices — produces a four-root-cause diagnostic for silos, an Engineering Guilds framework, a minimum-viable documentation approach using ADRs, a structured onboarding model, and a cross-team request decision framework. Use when the user says "knowledge silos," "reinventing the wheel," "nobody reads docs," "onboarding is bad," "teams don't talk," "documentation culture," "cross-team friction," "information doesn't flow," or "new hires struggle to ramp up."
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.