yaml-only-skill
This skill has proper frontmatter but absolutely no body content. No instructions, no steps, no examples, nothing after the frontmatter.
This skill has proper frontmatter but absolutely no body content. No instructions, no steps, no examples, nothing after the frontmatter.
Starknet network-level constraints and protocol facts that impact contract safety and agent reasoning.
Read and edit NixOS module options. Validate before applying. Show diffs before rebuild. Enumerate available options. Understand the NixOS declarative model deeply.
Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect). Use after clarification is complete, before routing to specialist agents. Ensures agents receive complete context for effective work.
Template and guide for creating skills. Demonstrates the standard skill structure with resources, docs, examples, and templates directories. Use this as a reference when building new protocol integrations.
Function decorators for automatic type conversion, batch processing, caching, timeout protection, deprecation, and lifecycle management. Use when writing scientific computing functions that need to accept multiple array types or require performance optimizations.
devbooks-spec-contract:定义对外行为规格与契约(Requirements/Scenarios/API/Schema/兼容策略/迁移),并建议或生成 contract tests。合并了原 spec-delta 和 contract-data 的功能。用户说"写规格/spec/契约/OpenAPI/Schema/兼容策略/contract tests"等时使用。
devbooks-proposal-challenger:对 proposal.md 发起质疑(Challenger)+ 查漏补缺,指出风险/遗漏/不一致并给结论,发现缺失的验收标准和未覆盖场景。用户说"质疑提案/挑刺/风险评估/提案对辩 challenger/查漏补缺"等时使用。
devbooks-proposal-judge:对 proposal 阶段进行裁决(Judge),输出 Approved/Revise/Rejected 并写回 proposal.md 的 Decision Log。用户说"裁决提案/提案评审/Approved Revise Rejected/decision log"等时使用。
Squash-merge the open pull request for the current branch and clean up the branch, only when that PR exists and all checks pass. Use when the user asks to merge a PR, finish a PR, land a PR, or complete a pull request from the branch they are on. Never ask for a PR number; the skill applies only to the PR tied to the checked-out branch.
Configure and distribute creator fees to multiple shareholders using the PumpFees program with BPS-based share allocation, admin management, and cross-program fee consolidation for graduated tokens.
Audit save and load behavior for ADR-031 schema contracts, invariants, and round-trip safety.
Read release-plan state and select the next ADR-compliant actionable development step.
Author or revise ADR files and release-plan ADR entries; use for new ADR drafts, status transitions, and ADR governance updates.
Map a proposed change to governing ADRs and constraints before implementation; use for ADR applicability and conflict checks.
Adversarially challenge cleanup and test proposals for hidden risk, weak evidence, and coverage or behavior regressions, including Option A/B/C focus-specific risks.
Analyze ADR compliance by interpreting the ADR's intent, verifying that implementation and RTD satisfy every decision, and producing a dated gap report with only unresolved items.
Always use emacsclient instead of emacs. This applies to all Emacs operations: user requests, byte compilation, check-parens, running ERT tests, and any other elisp evaluation.
Help with AbacatePay payment integration in Next.js projects. Use when implementing PIX payments, managing subscriptions, handling webhooks, or debugging payment flows. Covers SDK usage, webhook verification, and billing management for Brazilian SaaS applications.
Use this skill when you need to review and refactor code to make it simpler, more maintainable, and easier to understand. Helps with identifying overly complex solutions, unnecessary abstractions.
View Polyhub portfolio stats, fee history, and place manual orders with explicit confirmation and field validation.
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes.
Quick startup checklist for factory supervisors. Use at the beginning of a factory session to load context, check EPICs, and confirm worker availability.