Best practices for orchestration-ready task files. Enforces adversarial testing, skill chain syntax, definition-of-done requirements, gate definitions, persona routing, and /model directives. Referenced by /plan and /review-plan.
Best practices for porting features from one codebase, app, harness, TUI, API, or workflow into another without losing destination-specific behavior. Use when users ask to port, clone, migrate, replicate parity, achieve functional equivalence, borrow features, compare source vs destination, or preserve custom work…
Standards and workflow for creating root-level PROJECTSTATE.md reports from local receipts, project knowledge, stale/aspirational audits, competitor research, and external reviewer evidence. Use when asked for project state, comprehensive project review, "what works and what is missing", stale code/doc assessment…
Repo-specific Python best practices for agentic coding: Loguru + Typer + uv + pyproject.toml, httpx over requests, functions-first, module docstrings, max 800 LOC per file, and non-mocked sanity tests.
React, Next.js, React Native, and web design best practices from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js/React Native components, optimizing performance, auditing UI accessibility, or designing component APIs. Triggers: "review react", "optimize component", "check accessibility"…
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Standards and templates for writing concise, welcoming, evidence-aware README.md files for agent-skills skills, public project pages, gallery card destinations, architectural playground repos, and developer-facing docs. Use when creating or reviewing README prose, README structure, project/skill landing pages…
Canonical map and shared contracts for the agent-governance ecosystem: the pi.receiptenvelope.v1 boundary envelope, the component graph, and the rules for which component owns which schema. Use when wiring a skill or extension into the shared receipt world, when asking how shame, triage-error, tau, ask…
Best practices for using Chatterbox and Chatterbox Turbo as an emotional voice renderer: memory-grounded utterance planning, native paralinguistic tags, spaced ellipsis pauses, renderchunks pauseafterms, intensity/valence routing, reference-audio selection, and retained analyzer evals. Use when coding or reviewing…
FastAPI best practices for Python control-plane services, async eval APIs, Pydantic contracts, OpenAPI surfaces, security dependencies, deployment handoffs, and Flask fallback adapters. Use when building, reviewing, or converting FastAPI/Flask services, especially skill-backed cyber-safety eval control planes.
Canonical rules for writing, formatting, exporting, and verifying Graham Anderson's resume and its public surfaces, so an agent never re-derives them by trial and error. Use when editing RESUME.md, changing the resume PDF, DOCX, Markdown or /resume page, reconciling LinkedIn with the resume, deciding page count or…
Best practices for leading multi-model Ask roundtables and Tau-DAG deliberation panels. Use when a user asks for a roundtable, model panel, mixed web/API collaborator discussion, multi-round critique, attributed dissent synthesis, or guidance on turning several model perspectives into executable next steps through…
Repo-specific Rust best practices for agentic coding: thiserror + anyhow error handling, tokio async runtime, tracing for observability, clap for CLI, axum for HTTP, serde patterns, cargo workspace conventions, ownership and lifetimes, and idiomatic Rust 2024 edition patterns.
Error recovery and anti-patterns for scillm LLM proxy. Load this when scillm calls fail, timeout, or return unexpected results. Covers batch sizing, header requirements, model selection, and debugging workflow.
General application, service, plugin, and agent security hardening baseline. Use before /hack, /security-scan, /code-runner probe generation, or security review. Grounded in OWASP ASVS, OWASP Cheat Sheet Series, Node.js security guidance, and agent/plugin trust-boundary lessons.
Deterministic coded self-improvement loops for -lab skills. The agent will NOT do this reliably — loops MUST be in code. Proven pattern from Classifier Lab: dataenrichment.py + trainingloop.py.
Best practices for designing and structuring agent skills: SKILL.md frontmatter rules, triggers, progressive disclosure, and when to use scripts vs references.
★not rated 6▲
+1
changed todayA37 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: