.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/codybrom/clairvoyance
home/skills/codybrom/clairvoyance
codybrom avatar

codybrom/clairvoyance

16 skills

View on GitHub
$npx skills add codybrom/clairvoyance
SkillInstalls
abstraction-qualityEvaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow.—code-evolutionEvaluates whether changes to existing code maintain or degrade design quality.—comments-docsReviews comment quality and documentation practices: the four comment types, comments-first workflow, and comment rot.—complexity-recognitionDiagnoses whether complexity exists and where it comes from, using the three-symptom, two-root-cause framework.—deep-modulesMeasures module depth: whether the interface is simple relative to the implementation behind it.—design-it-twiceGenerates and compares at least two fundamentally different design alternatives on concrete criteria before committing.—design-reviewOrchestrates a structured design review, running the other skills as a diagnostic funnel from complexity triage to a full red-flags sweep.—diagnoseRoutes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree.—error-designReviews error handling and exception design, applying the \"define errors out of existence\" principle.—general-vs-specialEvaluates whether interfaces are appropriately general-purpose.—information-hidingChecks for information leakage across module boundaries, including temporal decomposition and false encapsulation.—module-boundariesEvaluates where module boundaries are drawn and whether modules should be merged or split.—naming-obviousnessReviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit.—pull-complexity-downChecks whether complexity is pushed to callers or absorbed by implementations — the direction complexity flows.—red-flagsScans code against 17 design smells (the book's 14 named Red Flags plus 3 process-stage signals) and produces a structured diagnostic report.—strategic-mindsetAssesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns.—