Loading...
Loading...
Found 105 Skills
Legacy-project style inheritance skill. Use when the user types /inherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent "style drift" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.
Technical due diligence for M&A, investment, or acquisition. Reads a target company's codebase and generates a comprehensive tech DD report with architecture assessment, tech debt quantification, scalability analysis, security posture, team capability inference, build system quality, test coverage, deployment maturity, and open source license risks. Outputs tech-dd-report.md formatted like a real investment memo with risk ratings, remediation costs, and go/no-go recommendation.
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Analyzes codebase against standards and generates refactoring tasks for ring:dev-cycle.
Investigate Problem - analyzes a problem in the codebase and proposes actionable solutions
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.
Analyze codebase to design and implement comprehensive test coverage — top-down code analysis, bottom-up test design, edge case focus, existing test audit, and agent team execution
Generate or update project memory for AI agents — default to AGENTS.md, support agent-specific targets such as CLAUDE.md, and keep sibling memory files synchronized while capturing stable architecture, conventions, and operational knowledge
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding