nav-marker
Create context save points to preserve conversation state before breaks, risky changes, or compaction. Use when user says "save my progress", "create checkpoint", "mark this point", or before clearing context.
Create context save points to preserve conversation state before breaks, risky changes, or compaction. Use when user says "save my progress", "create checkpoint", "mark this point", or before clearing context.
Use when making internal function-to-function calls within a Pikku app, composing functions, or exposing RPC endpoints. Covers rpc.invoke, rpc.remote, rpc.exposed, and generated RPC client. TRIGGER when: code uses wire.rpc or expose: true, user asks about calling one Pikku function from another, function composition, or RPC endpoints. DO NOT TRIGGER when: user asks about HTTP routes (use pikku-http) or addon cross-package calls (use pikku-addon).
Work on Madoc TS runtime configuration, path conventions, and Docker build/runtime setup. Use when adjusting env vars, file paths, or Docker build steps in services/madoc-ts.
Understand and extend the Madoc TS extension framework. Use when adding extensions, registry definitions, or plugin-backed extension behavior in services/madoc-ts.
Document the execution container (VM), request-level TempVM, and parser-level sub-interpreters (statement parsers) in the Origami PHP runtime. Use when the user asks about the interpreter design, runtime container, or wants to update related documentation.
Patterns for writing BTST backend plugins inside the monorepo, including defineBackendPlugin structure, getters.ts/mutations.ts separation, the api factory, lifecycle hook naming conventions, and accessing the adapter in AI tool execute functions. Use when creating or modifying a backend plugin, adding DB getters or mutations, wiring the api factory, or implementing lifecycle hooks in src/plugins/{name}/api/.
Work on Madoc TS frontend structure for site and admin. Use when changing React routes, SSR render entrypoints, shared utilities, or component organization in services/madoc-ts.
Build, run, and debug the Madoc Docker/compose stack with the Docker daemon already running, including rebuilding images, starting/stopping services, inspecting containers/images, and using pm2 inside the madoc-ts container (server/queue/scheduler/auth) plus frontend rebuilds for volume-mounted assets.
Create a new Agenvoy script tool (JavaScript or Python) stored at ~/.config/agenvoy/script_tools/. Use when asked to create, add, or generate a script tool. A script tool is a local executable invoked by the agent via stdin/stdout JSON.
Capture a session's repeatable process into a reusable SKILL.md file following the agentskills.io standard. Use when the user says "skillify this", "turn this into a skill", "capture this as a skill", "make this repeatable", "save this workflow", or "create a skill from this session". Works at end of any workflow worth repeating.
Capture a session's repeatable process into a reusable SKILL.md file following the agentskills.io standard. Use when the user says "skillify this", "turn this into a skill", "capture this as a skill", "make this repeatable", "save this workflow", or "create a skill from this session". Works at end of any workflow worth repeating.
Structured dev workflows via /brainstorm, /write-plan, /execute-plan. Use when breaking down complex projects into systematic steps.
Frontend aesthetics policy. Use when building UI, components, landing pages, dashboards, or any frontend work. Prevents generic ai-generated look.
Prompt engineering for production LLMs — structured outputs, RAG, tool workflows, and safety. Use when designing or debugging prompts for LLM APIs.
Automatically discover distributed systems skills when working with consensus, CRDTs, replication, partitioning, and distributed algorithms
Refactor codebases using Design by Typed Holes methodology - iterative, test-driven refactoring with formal hole resolution, constraint propagation, and continuous validation. Use when refactoring existing code, optimizing architecture, or consolidating technical debt through systematic hole-driven development.
Backend architecture policy. Use when building APIs, services, data access, or any backend work. Prevents over-engineering.
REST/GraphQL/gRPC/tRPC API design patterns. Use when designing APIs, writing OpenAPI specs, versioning, auth, or rate limiting.
Dependency management across npm, pip, cargo, and maven. Use when managing lockfiles, security scanning, versioning, or monorepo workspaces.
Guidelines and workflow for working on Laravel 11 or Laravel 12 applications across common stacks (API-only or full-stack), including optional Docker Compose/Sail, Inertia + React, Livewire, Vue, Blade, Tailwind v4, Fortify, Wayfinder, PHPUnit, Pint, and Laravel Boost MCP tools. Use when implementing features, fixing bugs, or making UI/backend changes while following project-specific instructions (AGENTS.md, docs/).
Production-grade frontend for Next.js, Vue, Angular, and Svelte. Use when building UI, fixing hydration errors, or setting up a new web project.