Comments
Code comments and annotations
intra-doc-links
by tomevault-io
Use when writing or editing a Rust doc comment that references a type, method, or module — link the reference so renames are caught by rustdoc.
dev-prose-standard
by xoykor
Use when writing, reviewing, restoring, trimming, or auditing prose in any codebase — deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings, and keeping every factual contract while removing reasoning transcripts, repetition, and decoration.
morning-triage
by luxtelos
Discovery — scan GitHub issues (and anything else the project names) for work, rank it, and append rows to state/triage.md at status new. Never modifies or closes existing rows.
python-guidelines
by viktor-ferenczi
Guiding principles for writing clear, concise, human readable and maintainable Python code.
masm-padding
by tomevault-io
Enforce stack padding conventions for Miden Assembly (.masm) procedures based on invocation type (call vs exec). Use when editing, reviewing, or creating .masm procedures, especially those with Invocation annotations. Use when this capability is needed.
dev-doc-standards
by xoykor
Use when writing, moving, reviewing, or auditing documentation in any repository — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, or for requests like "improve the docs", "audit the docs", "where should this be documented", or "this doc is too long".
behavioral-modes
by GilvanS
AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
review-prototype
by amitdialpad
Make a finished browser prototype commentable, publish it through its existing preview host, and return one shared review session with route-specific links. Use for stakeholder or customer prototype review; not for production release or arbitrary third-party websites.
testing-discipline
by SApplefeld
"Use when writing a test, deciding whether a change earns one or whether a test already in the tree still earns its keep, choosing which tests to run after a fix, or reading a red or a wall-clock figure. Triggers: a new test or test file, a test whose subject moved or was deleted, a suite audit, a test that reds on every intentional edit, a fix round tempting a full-suite re-run, a suite that reds only beside a busy neighbor, a wall clock that grew, a test reaching for a port, a spawn, or shared state."
ask-explaining-code
by NavanithanS
Explain code via analogies, ASCII diagrams, step-by-step walkthroughs.
documentation-templates
by GilvanS
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
code-review
by amywork777
Review GitHub pull requests with the Code Review tools - list what is waiting on the person, read a pull request's checks, diff and comment threads, show it to them in a tab, and post comments or reviews only when they ask.
velt-comments-best-practices
by velt-js
Velt Comments implementation patterns and best practices for React, Next.js, and web applications. Use when adding collaborative commenting features, comment modes (Freestyle, Popover, Stream, Text, Page), rich text editor comments (TipTap, SlateJS, Lexical), media player comments, or chart comments.
issue-investigation
by tomevault-io
Investigate GitHub issues for the mimo2codex project. Fetch issue details, reproduce problems, analyze root causes, and provide solutions. Use when the user reports a bug, shares an issue URL, or asks to investigate a problem. Use when this capability is needed.
harness-review
by cenron
Review the dev-workflow harness with the user. Aggregate milestone metrics and retros from the projects the user picks, find patterns, and draft a kit proposal with a predicted effect. On demand only; run from the workspace root.
yggdryl-types
by Platob
Declare yggdryl types and values in Rust, Python and Node.js - parse DataType expressions (Arrow, SQL, Hive, Spark, FIX spellings), build and edit Field schemas (non-null Struct root, metadata, PARQUET:field_id, comment, protocol views, FIELD:enum) and read values through DataType.scalar / Field.scalar into Scalar. Use when choosing a column type (decimal, timestamp/datetime64 zone, string or bytes leaf, uuid, geometry/geography WKB, ccy/isin/forex codes, the side, marketdatakind and state enums, an enumerated StringEnum column, serie/map/union), declaring a schema (Field::new, Field(...), new Field, yggdryl.int64 / fields.int64, @scalar dataclasses, into_field / intoField), adding, replacing or removing a column (set_field, remove_field, unnest_fields), an Arrow/pyarrow schema in or out (from_arrow_schema), converting values (Scalar.from_ / Scalar.from, as_py / asJs) or merging, diffing and walking schemas by path.
explain-like-senior
by manastalukdar
Senior-level code explanations with deep technical insights and context
dev-find-simplifications
by xoykor
Use when asked to find non-obvious simplification candidates in a codebase — dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces — to audit broad areas, or to fold worthwhile simplification ideas from another branch into the current work.
ship
by tomevault-io
Use when the user wants to commit, push, and open a pull request for the current changes. Stages relevant files, writes a descriptive commit message, pushes the branch, opens a PR against main, and posts an /oc review comment so opencode automatically reviews and approves if ready.
clean-code
by GilvanS
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
csharp-style
by SApplefeld
"My C# house style. Use whenever writing or modifying ANY C# code: new services, handlers, helpers, MediatR notifications, models, DI registration, or refactoring existing C#. Signature traits: #region organization, section comments ending in periods, grouped fields with label comments. Trigger on any C# work even when style is not named."
dev-code-review
by xoykor
Use when reviewing a pull request or changeset in any repository — orients the reviewer to the codebase's own standards (AGENTS.md conventions, defensive patterns, quality gates) and applies review-specific checks that code alone cannot show, including intent/interface contracts, lifecycle and concurrency, scope and necessity, model-visible behavior, test strength, and evidence.
just-init
by fredericosantos
Navigate Python codebases by reading init.py files before opening other files in a package. Maintain every init.py as living documentation: a top-level docstring containing a one-line package description, a file tree of .py files and subdirectories, and a brief purpose for each entry. Use when: (1) exploring or navigating a Python codebase, (2) creating new Python packages or modules, (3) adding, removing, or renaming files within a Python package, (4) onboarding to an unfamiliar Python project.
yggdryl
by Platob
Routes yggdryl work to the right layer and states the conventions every yggdryl API shares (install and features, naming, defaults, errors, streaming, zero copy) across the Rust crate, the Python wheel and the npm package - Arrow-native schemas (DataType, Field, Scalar), columns (Serie), storage handles (IOBase over local files, ZIP, S3/GCS/Azure, HTTP(S)), record media (Arrow IPC, Parquet, Avro, text, Iceberg), JSON/YAML/TOML/XML, URIs, expressions, xxHash/TxHash, FIX and market data. Use when installing or importing yggdryl, choosing which yggdryl API answers a task, translating yggdryl code between Rust, Python and Node.js, or before any other yggdryl-* skill.