layer-07-data-model
Expert knowledge for Data Model Layer modeling in Documentation Robotics
发现 documentation architecture patterns 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Expert knowledge for Data Model Layer modeling in Documentation Robotics
Expert knowledge for Security Layer modeling in Documentation Robotics
Codex MCP 协作流程。触发场景:(1) 新功能开发 (2) 重构 (3) 复杂业务逻辑 (4) 代码审查。提供三阶段协作:需求分析→原型获取→审查,强调批判性思考与只读安全。
Koin dependency injection framework for Kotlin. Use for Kotlin DI, Android development, Ktor backend, Compose Multiplatform, dependency injection patterns, and module definitions.
Use for pragmatic technical design decisions - applies DHH / Rails philosophy of simplicity, convention, and shipping. Extremely pragmatic, first-principles thinking, minimalist in tech, challenges the status q...
Universal methodology for discovering and adapting to any codebase's patterns, conventions, and architectural decisions. Automatically detects technology stack, learns project structure, and identifies coding s...
Create detailed technical plans and implementation roadmaps by analyzing project architecture and designing solutions that integrate seamlessly with existing patterns. Use when designing features, planning inte...
设计高性能后端架构,Rust/C++ 底层开发,分布式系统设计
End-to-end project orchestration from idea to implementation. Use when user wants to build a complete project, implement an MVP, or says "build this app/feature". Coordinates product-design, architecture, task-...
Break down PRD and Architecture into implementable engineering tasks. Use when user wants to create a task list, plan implementation work, decompose features into stories and tasks, or needs to translate requir...
Ensure code follows DDD architecture and DAL separation principles. Triggers: DDD, arch, 架構, 新功能, 新模組, new feature, scaffold, 骨架, domain.
Proactively detect and execute code refactoring to maintain DDD architecture and code quality. Triggers: RF, refactor, 重構, 拆分, split, 模組化, modularize, 太長, cleanup.
Principal Engineer focused on maintainability, SOLID principles, and clean code.
Design systems for change. Trade-off analysis, ADR documentation, pattern selection. Architecture decisions must have documented rationale.
Professional skepticism with pattern enforcement. Verify before agreeing, challenge violations, propose instead of asking. Concise output, research before asking, answer questions literally.
Add retry, timeout, and circuit breaker patterns at the workflow level. Business functions stay clean.
Software design beyond syntax. Fail-fast over fallbacks, explicit over implicit, composition over inheritance. Integrates with fn(args, deps) and Result type patterns. Includes 8-dimension design analysis.
Never throw for expected failures. Use Result types with explicit error handling and workflow composition.
Enforce the fn(args, deps) pattern: functions over classes with explicit dependency injection
Design system principles for distinctive, implementation-ready interfaces. Context before design, show don't tell, every state documented.
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
Create multi-step workflow skills with progressive step loading, state management, and interactive decisions. Use when building complex skills like APEX that need structured phases.
Apply when improving code structure without changing behavior: reducing duplication, simplifying complexity, or improving readability.
Apply when containerizing applications: writing Dockerfiles, docker-compose configurations, and multi-stage builds.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。