diagram
Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.
Discover lifestyle architecture patterns skills, compare source repositories and read the instructions for each workflow.
Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.
Interactive planning skill for Amp. Generates specs, implementation plans, and loop infrastructure through clarifying questions.
Review and simplify code to reduce complexity and improve maintainability
Language-agnostic rulebook for producing, reviewing, and improving elegant code. Use when writing new code, refactoring existing code, reviewing code quality, or when user asks for "elegant", "clean", "maintain...
Migrate Rust code from sacp v1.x to v2.0 role-based API. Use when upgrading sacp dependencies, fixing Builder errors, or when code references MessageAndCx or old connection patterns.
Coding standards, modular architecture, and common execution patterns for the PolyFlup Python backend.
Core patterns for data fetching, state management, and user preferences. Use when implementing new features that require getting data from Our APIs, Morpho API, on-chain states or managing shared state.
Architecture patterns for organizing feature modules in the codebase. Use when creating new files, brand new features or pages.
Transform nebulous ideas into sharp, testable frameworks through multi-perspective dialectical interrogation. Use when developing vague intuitions, pressure-testing concepts, structuring half-formed frameworks,...
Intermediate scope for inheritance — like OpenLaszlo's
Rooms as pipeline nodes, exits as edges, objects as messages
Two-pointer reversible cursor worms for traversal and dataflow
Many turns in one call. Instant communication. No round-trips.
Factorio-style logistics — items flow automatically between containers
Reference for project architecture. Use when you need to understand the codebase structure, module organization, request/response flow, or key types.
Apply Model-First Reasoning (MFR) to code generation tasks. Use when the user requests "model-first", "MFR", "formal modeling before coding", "model then implement", or when tasks involve complex logic, state m...
Apply startup execution wisdom to product, strategy, and business decisions. Use for feature prioritization, build-vs-buy decisions, go-to-market planning, pricing, hiring, scope/timeline reality checks, or whe...
Expert Django and Celery guidance for asynchronous task processing. Use when designing background tasks, configuring workers, handling retries and errors, optimizing task performance, implementing periodic task...
High-level architecture decisions, patterns, and project structure. Use when user asks about architecture decisions, project structure, pattern selection, or mentions how to organize, which pattern to use, best...
Action-oriented architecture for Laravel. Invokable classes that contain domain logic. Use when working with business logic, domain operations, or when user mentions actions, invokable classes, or needs to orga...
Multi-tenant application architecture patterns. Use when working with multi-tenant systems, tenant isolation, or when user mentions multi-tenancy, tenants, tenant scoping, tenant isolation, multi-tenant.
Reduce complexity by revealing information progressively. Use when designing onboarding, complex forms, feature-rich interfaces, or any experience where showing everything at once would overwhelm users.
DBOS durable execution patterns and CRITICAL constraints for ChainGraph executor. Use when working on workflows, steps, execution, or any DBOS-related code. Contains MUST-FOLLOW constraints about what can be ca...
Core ChainGraph domain concepts - flows, nodes, ports, edges, and execution. Use for ANY ChainGraph development to understand the fundamental abstractions. Explains what flows are, how nodes process data, port...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.