ringwriting-plans
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context.
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context.
Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.
Semantic code search by meaning. Use codebase_peek to find WHERE code is (saves tokens), codebase_search to see actual code. For exact identifiers, use grep instead.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...
Browser automation for testing, screenshots, and web interaction. Use when navigating pages, clicking elements, filling forms, taking screenshots, or automating browser tasks.
Queries Sentry for issues, events, traces, and error analysis. Use when debugging production errors, searching issues, analyzing traces, or getting AI root cause analysis with Seer.
Autonomous task loop that picks ready tasks, implements them in new threads, commits, and repeats. Use when asked to "ralph", "use a ralph loop", or "ralph this".
Streamlit page authoring patterns for AGILAB (session_state safety, keys, rerun, UX).
Runbook for working in the AGILab repo (uv, Streamlit, run configs, packaging, troubleshooting).
Documentation workflow for AGILAB (sources vs generated HTML, public constraints, consistency checks).
Guidance for installing AGILAB, installing apps/pages, and debugging install/test failures.
Quick, targeted test strategy for AGILAB (core unit tests, app smoke tests, regression).
Guidance for using local LLM backends (Ollama/GPT-OSS) inside AGILAB with correctness-first prompts.
Validate plugin integrity and offer safe auto-fixes for common issues - checks agents, skills, hooks, routing config, and plugin structure
Validates PopKit code quality using concrete metrics for DRY, coupling, cohesion, and architectural patterns
Multi-project dashboard for managing PopKit-enabled projects. Shows health scores, recent activity, and quick actions across all registered projects. Use when switching between projects, checking overall status...
Curated project templates that guide feature-dev Phase 3 questions with research-backed technology choices. Provides standardized options for common project types (SaaS API, ML Service, CLI Tool, Full-Stack). U...
Use when starting work on an unfamiliar project or needing to understand a codebase - performs comprehensive analysis discovering architecture, patterns, dependencies, testing coverage, and improvement opportun...
Captures research insights, decisions, and learnings during development. Use after completing spikes, making architectural decisions, or discovering important patterns. Prompts for context and rationale, stores...
Start-of-day setup and readiness routine. Calculates Ready to Code Score (0-100) based on session restoration, service health, dependency updates, branch sync, PR reviews, and issue triage. Automatically captur...
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context. Assumes skilled developers who need domain-specific gui...
Evaluates PopKit user experience using concrete heuristics for command naming, error messages, and interaction patterns
Initialize .claude/ structure and surgically add PopKit section to CLAUDE.md without overwriting. Detects conflicts, creates config, prompts for Power Mode. Use for new projects only - use analyze-project for e...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.