Results for “out-of-tree-modules”

ai-module-development

Estructura aplicaciones Flutter en módulos independientes y reutilizables con flutter_modular, incluyendo diseño de paquetes, dependencias y configuración de Melos.

Outlines — structured generation with guaranteed JSON/regex output from local LLMs

module-development

Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation.

Imported skill utils from langchain

Creates, reviews, debugs, and modernizes Python project structure with deterministic tooling including pyproject.toml, uv, Ruff, Pyright, and pytest.

clawhip × filesystem-offloaded memory

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Designs, reviews, and scales backend systems with detailed blueprints, trade-off analysis, and technology recommendations.

Sets up {module-name} module in a project. Use when the user requests to 'install {module-code} module', 'configure {module-name}', or 'setup {module-name}'.

Architects, reviews, and scales backend systems with structured blueprints, trade-off analysis, and audit reports.

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

Provides a comprehensive reference for the Move programming language, covering its resource-oriented philosophy, type system, abilities, and safety guarantees for Sui and Aptos blockchains.

Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

Pattern for deprecating external dependencies while maintaining backward compatibility. Trigger: removing Java/FIJI/MATLAB, deprecating optional deps

Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.

Ownership models are usually inherited rather than chosen, and the inherited one

Converts Stitch designs into modular Vite and React components, using MCP networking and AST-based validation to ensure code quality.

Provides a higher-level map of relevant modules and callers using the project's domain glossary when you're unfamiliar with a code area.

MONOPOLY is a Senior System Design Engineer skill for architecting, reviewing, and scaling systems. Triggers on requests involving architecture, databases, scaling, microservices, or infrastructure de

Atomic-design guidance for Templates — page-level wireframes that arrange organisms into layout slots (hero/main/sidebar/footer) without fetching data. Use when authoring components under ui/templates, defining reusable page skeletons, or keeping layout decisions out of pages and organisms.