Results for “reference-implementations”

Load this skill when the user says "implement issue", "implement-issue", or "/implement-issue". Implements a GitHub story issue end-to-end: prepares base branch, creates feature branch, implements the requirements, verifies via the verify-implementation skill, and opens a PR.

Implement a piece of work based on a spec or set of tickets.

Implements work from a PRD or set of issues using TDD, typechecking, and regular testing, then reviews and commits the changes.

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

Comprehensive guide for implementing code incrementally following established patterns, conventions, and quality standards

Implements a piece of work from a spec or ticket set. Use when the user says "implement this spec", "work the tickets", or wants code written from an existing plan.

Implement a piece of work based on a spec or set of tickets.

Ingests case studies, past proposals, and boilerplate from library/inbox into structured indexes. Use when the user requests to 'index proposal library', 're-index case studies', 'ingest inbox docs', or 'validate library'.

Index of cloned framework repos for Maks's reference during builds.

Implements features and writes code based on Plans.md tasks, with quality gates and routing to sub-skills for feature implementation and test writing.

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Plan, debug, tune, evaluate, export, or deploy public Nemotron embedding and reranking retrieval recipes using the current checkout.

Supabase-first reference and implementation skill for Nick's app stack. Use when writing Supabase queries, auth flows, RLS policies, storage rules, realtime features, edge-function integrations, migrations, or debugging Supabase behavior. Prefer this instead of guessing Supabase APIs or patterns. Bias toward product-led implementation choices, trust-aware access control, MVP discipline, and using only the Supabase features the product actually needs.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Adapt and integrate a specific pattern from your references into your current codebase. Use when you've identified a pattern worth adopting and need a structured plan to integrate it with minimal disruption.

Comprehensive guide to bpe. Master the concepts, implementation, best practices, and real-world applications of bpe in professional environments.

Writing Plans

Executes a written implementation plan in a separate session, reviewing it critically, running tasks with verification, and stopping to ask for help when blocked.

Comprehensive guide to recoil. Master the concepts, implementation, best practices, and real-world applications of recoil in professional environments.

处理和分析用户上传的文件引用，提取关键信息并提供应用建议。适用于解析@符号引用、自然语言引用、提取短剧策划相关信息

Use when implementing go functionality with production-grade patterns and safeguards.

Comprehensive guide to relu. Master the concepts, implementation, best practices, and real-world applications of relu in professional environments.

Comprehensive guide to hive. Master the concepts, implementation, best practices, and real-world applications of hive in professional environments.

Comprehensive guide to dino. Master the concepts, implementation, best practices, and real-world applications of dino in professional environments.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

.cursor 仅做引用。规则/技能/计划主仓在 dev/ai。新增/修改必须在 dev/ai 下操作。

Gtd reference tool. Use when working with gtd in life contexts.

Compare MoonSpec story breakdown output against the current repository implementation, preserve fully implemented stories as skipped, narrow partially implemented stories to remaining work, and rewrite the story breakdown handoff before issue creation.