Explorar skills

Ultra-compressed Thai+English communication mode. Cuts ~60-75% of tokens by speaking simple Thai while preserving technical accuracy. Triggers: - "/pordee" / "/pordee full" / "พอดี" / "พอดีโหมด" / "พูดสั้นๆ" → enable full - "/pordee lite" → enable lite - "/pordee stop" / "หยุดพอดี" / "พูดปกติ" → disable - "/pordee-stats" / "/pordee-stats --share" → show token usage stats

Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /pordee-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.

Refactor, simplify, or clean up code for improved maintainability without changing business logic

Documentação e padrões para usar motion-sv, uma adaptação para Svelte 5 do Motion (Framer Motion). Use isso quando o usuário desejar animações, gestos ou transições no Svelte.

Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.

Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.

Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase for patterns", "find all [domain concept]", or needs mechanism-level understandin

Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership. Ensures MECE coverage (no overlap, no gaps) and that ALL test categories including E2E are executed.

Unified codebase discovery across structure navigation, tech-stack detection, and documentation extraction. Use when onboarding to a project, locating implementation paths, identifying frameworks/tooling, or validating docs against code reality.

Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill doesn't work" complaints.

You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.

Validate in any of six modes — spec quality, single-file review, spec-to-implementation drift, constitution rule enforcement, comparison between two artifacts, or sanity-checking your understanding. Use when checking a spec by ID, validating a file by path, detecting drift, enforcing constitution rules, comparing two sources ("$X against $Y"), or asking a freeform validation question.