Elmmly
OrganizationSpecialized AI genies for product discovery and delivery, from opportunity mapping to spec-driven implementation.
Categories
Indexed Skills (10)
architecture-awareness
Ensures ADR and C4 diagram behaviors during all workflows. Use when loading context, discussing architecture, creating designs, or when "ADR", "architecture decision", "C4", "coupling", "cohesion", or "boundary" are mentioned. Activates during /arch:init, /context:load, /context:refresh, /spec:init, /define, /design, /deliver, /discern, /handoff, /diagnose, and /discover.
brand-awareness
Ensures brand-consistent behavior during workflows. Auto-activates when brand guide exists and "brand", "brand spec", "design tokens", "brand consistent", or "visual identity" are mentioned. Activates during /brand, /brand:image, /brand:tokens, /design, /deliver, /discern, /handoff, /context:load, and /context:refresh.
code-quality
Enforces code quality standards when writing or editing code. Use when implementing features, fixing bugs, or refactoring. Ensures error handling, no hardcoded values, proper patterns, and security considerations.
conventional-commits
Creates conventional commit messages following commitlint standards. Use when committing code, creating git commits, or when the user says commit, push, or save changes.
debugging
Structured root cause investigation for any reported bug, regression, or failed fix. Use when a user reports a bug or runtime misbehavior, when a test fails that you expected to pass, when a previous fix attempt didn't work ('the fix didn't work'), or when an error occurs during implementation. Reproduce first; find the root cause before patching.
pattern-enforcement
Enforces project patterns and architecture conventions. Use when designing systems, implementing features, or reviewing code structure. Ensures consistency with established patterns.
spec-awareness
Ensures spec-driven behavior during all workflows. Use when loading context, discussing project structure, starting features, or when "spec", "specification", "acceptance criteria", or "bootstrap" are mentioned. Activates during /context:load, /context:refresh, /spec:init, /define, /design, /deliver, /discern, /handoff, /done, and /discover.
stack-awareness
Ensures tech-stack-aware behavior during workflows. Auto-activates when stack profile rules exist in .claude/rules/stack-*.md. Activates during /arch:init, /context:load, /context:refresh, /deliver, /discern, /diagnose, and /handoff.
tdd-discipline
Enforces test-driven development with Red-Green-Refactor cycle. Use when writing new code, implementing features, fixing bugs, or when tests are mentioned. Ensures tests are written before implementation.
problem-first
Ensures problem-first framing before solutioning. Use when defining work, discussing features, handling requests that sound like solutions, or when someone says "we should add" or "let's build".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.