메뉴
이 저장소의 skills
SkillsMP는 tomevault-io/skills-registry에서 17,125개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
tomevault-io/skills-registry수집된 skill 17,125개 중 40개를 표시합니다.
Orchestrate comprehensive planning phase from ideation to development-ready specifications using 3 specialized agents (Full workflow documentation at docs/workflows/planning-workflow.md) Use when this capability is needed.
원문 언어: 영어
Orchestrate comprehensive 7-phase RBMAS research for multi-dimensional queries (4+ dimensions). Coordinates multiple specialist agents through SCOPE → PLAN → RETRIEVE → TRIANGULATE → DRAFT → CRITIQUE → PACKAGE methodology. Use for thorough internet research…
원문 언어: 영어
Orchestrate comprehensive TODAS research for novel/emerging domains (1-7 subagents adaptive). Specializes in unprecedented topics, post-training data, and emerging technologies. Uses adaptive depth-based methodology: straightforward queries (1 agent),…
원문 언어: 영어
Use when the user wants a minimal source-only archive for upload or checkpoint. Creates a tar.gz with just source and test files from all workspace crates.
원문 언어: 영어
Use when /performance-analyzer identifies a hot function, when /bench-compare shows regression and you need instruction-level analysis, or when you suspect bounds checks or register spills in a tight loop. ASM-guided optimization with cargo-show-asm +…
원문 언어: 영어
Use when designing safety-critical code, distributed protocols, or novel algorithms where getting the design wrong is expensive. Parallel research agents survey papers, production systems, and prior art, then synthesize into an evidence-backed codebase plan.
원문 언어: 영어
Use when facing a design decision with multiple viable approaches, when you want competing proposals evaluated objectively, or when brainstorming needs structured diverge-then-converge evaluation. 3-5 independent design agents plus ranked synthesis.
원문 언어: 영어
Use when adding or modifying coordination protocols, implementing consensus or gossip mechanisms, or changing distributed state management. Audits designs against academic literature and battle-tested systems with citation requirements.
원문 언어: 영어
Use when /doc-rigor has written or updated documentation and you need independent accuracy verification, or when existing docs may contain stale API claims or wrong command examples. Fresh-agent verification against code reality.
원문 언어: 영어
Use when you have code review findings, PR comments, or review reports that need to be systematically addressed — especially when there are multiple findings across different files and severities
원문 언어: 영어
Use when designing new public APIs, adding trait methods, or refactoring type signatures to ensure they are easy to use correctly and hard to use incorrectly. Reviews Rust interfaces for misuse resistance.
원문 언어: 영어
Use when modifying hot-path code in coordination or scanner engine, before merging performance-sensitive changes, or when CI benchmarks flag a regression. Performance regression testing with before/after comparison.
원문 언어: 영어
Use when writing hot-path code in coordination or scanner engine, before committing changes to scanner-engine modules, when benchmarks show unexpected regressions, or during optimization of gossip-stdx data structures. Static performance analysis.
원문 언어: 영어
Use when PR review comments claim a bug or incorrect behavior, when multiple reviewer comments need systematic triage, or when a correctness claim needs proof before changing code. Verify-first PR comment response with evidence-based fixes.
원문 언어: 영어
Use when preparing to merge a feature branch, after completing a significant implementation, or when critical code paths need deeper review than a single pass. Six parallel specialist agents plus ranked synthesis.
원문 언어: 영어
Use when modifying unsafe blocks, adding parsing or decoding logic, changing buffer pool or scratch internals, or before merging changes to data structure implementations with raw pointers. Memory safety and security audit.
원문 언어: 영어
Use when modifying gossip-coordination or coordination contracts, after adding trait methods to CoordinationBackend, after changing state machine transitions, or before marking coordination PRs ready. DST-compatibility code review.
원문 언어: 영어
Use when creating a new module in gossip-coordination, adding a gossip protocol component, or building a pipeline stage that touches distributed state. Generates DST-ready boilerplate with sans-IO pattern and proptest harnesses.
원문 언어: 영어
Use when /asm-forge shows autovectorization missed opportunities, when hot loops process arrays of bytes or integers, or when porting x86 SIMD to ARM NEON/SVE. Generates platform-specific intrinsics with correctness and performance validation.
원문 언어: 영어
Use when a test module has many similar unit tests, when repetitive assertions could be replaced by property-based or parameterized tests, or when test maintenance cost is high. Consolidates verbose suites into rstest, proptest, or fuzz tests.
원문 언어: 영어
Use when test suites feel bloated, when unit tests duplicate coverage already provided by property-based or simulation tests, or during periodic test hygiene. Identifies and removes redundant tests while keeping signal.
원문 언어: 영어
Use when adding or modifying unsafe blocks, when reviewing code that uses raw pointers or transmute, or before merging changes to types with unsafe internals. Audits safety invariants and demands benchmark+ASM proof of performance benefit.
원문 언어: 영어
Use when the user wants to package all source code into a tar.gz archive for upload or checkpoint. Creates a comprehensive archive excluding binaries and build artifacts.
원문 언어: 영어
Use when the user wants a minimal source-only archive for upload or checkpoint. Creates a tar.gz with just src/ and tests/ directories.
원문 언어: 영어
ASM-guided deep performance optimization. Collects assembly, audits codegen quality, applies targeted transforms, validates with benchmarks. Uses cargo-show-asm + Criterion as ground truth. Use when this capability is needed.
원문 언어: 영어
Deep research before design — 3-5 parallel research agents survey papers, production systems, failure modes, and prior art, then a synthesizer compiles evidence, and an integrator maps findings to a concrete codebase plan with citations Use when this…
원문 언어: 영어
Run a parallel diverge-then-converge design tournament — 3-5 independent agents explore a problem, then 2 ranking agents evaluate and stack-rank the results with confidence scores Use when this capability is needed.
원문 언어: 영어
Verify documentation accuracy against code reality and external claims — runs as a fresh agent after /doc-rigor to prevent confirmation bias Use when this capability is needed.
원문 언어: 영어
Performance regression testing workflow for hot path changes Use when this capability is needed.
원문 언어: 영어
Analyze Rust code for performance issues, allocation hot spots, and optimization opportunities Use when this capability is needed.
원문 언어: 영어
Parallel specialist code review — 6 focused agents (correctness, design, performance, safety, docs, complexity) diverge independently, then a single ranker merges findings into an importance-ranked report with confidence scores Use when this capability is…
원문 언어: 영어
Audit memory safety and security in unsafe code blocks, buffer handling, and security-sensitive operations Use when this capability is needed.
원문 언어: 영어
Consolidate verbose test suites by replacing repetitive unit tests with property-based tests, parameterized tests (rstest), or fuzz tests. Less code to maintain, same or better coverage. Use when this capability is needed.
원문 언어: 영어
Review test suites for duplicate, redundant, or low-value tests — especially unit tests already subsumed by property-based tests. Remove noise, keep signal. Use when this capability is needed.
원문 언어: 영어
Assess and recommend the appropriate testing strategy for Rust code - unit tests, property-based tests, fuzz tests, Kani model checking, or simulation testing Use when this capability is needed.
원문 언어: 영어
Adds testing & polish phases to existing tasks. Analyzes task phases, identifies frontend-touching work, generates test scenarios from success criteria, inserts testing-polish phases. Use when this capability is needed.
원문 언어: 영어
Creates structured task plans in docs/tasks/ with PRD and parallel phase enrichment. Use when user asks to "create a task" or "plan a feature". Auto-detects difficulty - simple tasks get inline enrichment, hard tasks get parallel agent enrichment.
원문 언어: 영어
Executes structured tasks from docs/tasks/ with phase-by-phase workflow. Use when user says "execute task", "run task", or provides task path. Reads CONTEXT.md for state, delegates phases to developer-agent, updates progress automatically. Use when this…
원문 언어: 영어
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling Use when this capability is needed.
원문 언어: 영어
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag Use when this capability is needed.
원문 언어: 영어