dean0x
UserThe most advanced agentic development toolkit for generating production-grade code. Ambient Orchestration, Working memory that never forgets. Self-learning workflows. Install once, forget about it. Your code gets better automatically.
Categories
Indexed Skills (40)
accessibility
This skill should be used when the user asks to "add accessibility", "check ARIA", "handle keyboard navigation", "add focus management", or creates UI components, forms, or interactive elements. Provides WCAG 2.2 AA patterns for keyboard navigation, ARIA roles and states, focus management, color contrast, and screen reader support.
go
This skill should be used when the user works with Go files (.go), asks about "error handling", "interfaces", "goroutines", "channels", "packages", or discusses Go idioms and concurrency. Provides patterns for error handling, interface design, concurrency, and package organization.
java
This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "Optional", "streams", "composition over inheritance", or discusses modern Java patterns and API design. Provides patterns for type system usage, error handling, immutability, and concurrency.
python
This skill should be used when the user works with Python files (.py), asks about "type hints", "protocols", "dataclasses", "async/await", "decorators", or discusses Pythonic patterns and data modeling. Provides patterns for type safety, error handling, data modeling, and async programming.
react
This skill should be used when the user works with React components (.tsx/.jsx), asks about "hooks", "state management", "context providers", "memo optimization", "useEffect", or discusses component composition and rendering performance. Provides patterns for hooks, state, effects, memoization, and React-specific architecture.
rust
This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "Result/Option", "traits", or discusses memory safety and type-driven design. Provides patterns for ownership, error handling, type system usage, and safe concurrency.
test-driven-development
This skill should be used when implementing new features, fixing bugs, or writing new code. Enforces RED-GREEN-REFACTOR.
testing
This skill should be used when the user asks to "write tests", "fix failing tests", "improve test coverage", "add integration tests", "debug a flaky test", or reviews test quality. Provides behavior-focused testing patterns, coverage analysis, and detection of brittle test anti-patterns like implementation coupling and non-deterministic assertions.
typescript
This skill should be used when the user works with TypeScript files (.ts/.tsx), asks about "generics", "type guards", "utility types", "strict typing", "discriminated unions", or discusses type safety and inference. Provides patterns for Result types, exhaustive checks, branded types, and type-safe API contracts.
ui-design
This skill should be used when the user asks to "design a component", "pick colors", "improve typography", "fix spacing", "choose a layout", or discusses visual design, CSS, styling decisions, or responsive interfaces. Provides patterns for typography scales, color systems, spacing, and production-grade UI design.
apply-decisions
Canonical algorithm for consuming DECISIONS_CONTEXT index — scan index, identify relevant entries, Read full bodies on demand, cite verbatim IDs inline.
apply-feature-knowledge
Consumption algorithm for FEATURE_KNOWLEDGE variable — pre-computed feature context
architecture
This skill should be used when reviewing code for SOLID violations, tight coupling, or layering issues.
boundary-validation
This skill should be used when the user asks to "validate input", "parse request data", "handle form data", "add Zod schema", "sanitize user input", or creates API endpoints and system boundaries. Provides parse-don't-validate patterns with schema validation for type-safe boundary enforcement and hostile input defense.
complexity
This skill should be used when reviewing code for high cyclomatic complexity, deep nesting, or long functions.
compliance
This skill should be used when reviewing code handling PII, payment data, health records, audit logs, data retention, or IaC under GDPR, HIPAA, PCI DSS, SOC 2, ISO 27001, or SOX.
consistency
This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
database
This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
dependencies
This skill should be used when reviewing dependency changes, lock files, or package additions.
dependency-research
This skill should be used when the user asks to "add a utility", "create a helper", "implement parsing", "build a wrapper", or writes infrastructure/utility code that may already exist as a well-maintained package. Enforces research before building.
design-review
This skill should be used when reviewing implementation plans for anti-patterns, checking design quality before implementation, or performing plan-level quality assessment. Provides 6 anti-pattern detection rules for the designer agent and inline planning.
docs-framework
This skill should be used when the user asks to "create a review report", "write a status log", "add documentation", "name this artifact", or creates files in the .devflow/docs/ directory. Provides naming conventions, templates, and directory structure for reviews, debug sessions, design docs, and all persistent Devflow documentation artifacts.
documentation
This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
feature-knowledge
Structures codebase exploration into a feature knowledge base
gap-analysis
This skill should be used when analyzing design documents, specifications, or plans for completeness gaps, architectural issues, security concerns, and performance implications. Provides focus-specific detection patterns for the designer agent.
git
This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", "manage branches", "fix merge conflicts", "undo a commit", "comment on a PR", "create a release", or performs any git/GitHub operations. Provides safety patterns, atomic commit formatting, PR descriptions, sensitive file detection, and GitHub API usage.
patterns
This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", "add configuration", or builds features involving database operations, REST/GraphQL APIs, pub/sub patterns, or service configuration. Provides implementation patterns that follow existing codebase conventions.
performance
This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
qa
This skill should be used when performing scenario-based acceptance testing, designing QA test plans, or validating that implementation behavior matches acceptance criteria beyond unit tests.
regression
This skill should be used when reviewing changes that may remove exports, change signatures, or alter behavior.
reliability
This skill should be used when reviewing code for unbounded loops, missing assertions, excessive allocation, or deep indirection.
research-codebase
Local codebase research — find patterns, trace flows, map dependencies without browsing the web
research-competitor
Competitor analysis — structured feature comparison, positioning analysis, and gap identification
research-external
External web research — find documentation, articles, and community knowledge with untrusted-data discipline
research-market
Market landscape research — analyze market positioning, user needs, and industry trends
research-technology
Technology evaluation — assess libraries, frameworks, and tools against project requirements
review-methodology
This skill should be used when performing a code review to apply the standard 6-step review process.
security
This skill should be used when reviewing code for injection flaws, auth bypasses, or hardcoded secrets.
software-design
This skill should be used when the user asks to "handle errors", "inject dependencies", "return Result", "make it immutable", "compose with pipes", or implements business logic, error handling, or service composition. Provides Result type patterns, dependency injection, immutability by default, pipe composition, and structured logging for robust application architecture.
worktree-support
Canonical worktree path resolution and discovery algorithm for agents and commands
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.