All authors
Claude Skills by cdeust
github.com/cdeust42 skills1 installs101 views
- Cortex AutomateSet up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to automate memory behavior based on conditions.Votes: 0GitHub stars: 73
- Cortex ConsolidateRun memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system healthy. Also use after importing many memories or at the end of a long session.Votes: 0GitHub stars: 73
- Cortex Debug MemoryDebug and fix memory system issues — validate memories, rate quality, manage protection, forget bad memories, and restore from checkpoints. Use when the user says 'fix memory', 'bad memory', 'wrong memory', 'delete this', 'protect this', 'this memory is wrong', 'memory quality', 'rate this memory', 'restore checkpoint', 'undo', or when memories are returning incorrect or stale results.Votes: 0GitHub stars: 73
- Cortex Explore MemoryExplore the memory system's state, find gaps in knowledge, assess coverage, and get diagnostic information. Use when the user asks 'what does my memory look like', 'show me memory stats', 'what am I missing', 'how good is my knowledge', 'memory health', 'show coverage', 'find gaps', 'what topics are weak', or when you need to understand the state of stored knowledge before a task.Votes: 0GitHub stars: 73
- Cortex ImportImport memories from other AI memory systems into Cortex. Supports claude-mem (SQLite), Claude Desktop sessions, ChatGPT web export (JSON), Gemini Takeout (JSON), Cursor conversations, and Claude Code JSONL. Use when the user says 'import from claude-mem', 'migrate memories', 'import ChatGPT history', 'import from Gemini', 'transfer memories', or when Cortex detects another memory system is installed.Votes: 0GitHub stars: 73
- Cortex Navigate KnowledgeNavigate the knowledge graph — trace entity relationships, explore causal chains, drill into memory clusters, and traverse co-access paths. Use when the user asks 'how are these related', 'what connects X to Y', 'show me the knowledge graph', 'trace the relationship', 'what caused X', 'drill down into', 'explore connections', or when you need to understand the web of relationships between concepts, entities, and memories.Votes: 0GitHub stars: 73
- Cortex ProfileView and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile' to rescan all session history, or 'list domains' to see all tracked project domains.Votes: 0GitHub stars: 73
- Cortex Recall GlobalSearch and retrieve global memories — knowledge that applies across all projects. Use when the user asks 'what are our coding standards', 'what conventions do we follow', 'what's our infrastructure setup', 'do we have a rule about', 'what applies to all projects', 'shared knowledge', 'global rules', or when you need cross-project context like architecture decisions, server configs, or team policies.Votes: 0GitHub stars: 73
- Cortex RecallSearch and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or architecture choices. Also use proactively when working on something that likely has relevant historical context.Votes: 0GitHub stars: 73
- Cortex Remember GlobalStore a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global rule', 'shared convention', 'infrastructure note', 'cross-project', or when the content is clearly universal (clean architecture, SOLID, deployment configs, server addresses).Votes: 0GitHub stars: 73
- Cortex RememberStore important decisions, patterns, errors, lessons, and context into Cortex persistent memory. Use when the user says 'remember this', 'save this', 'store this for later', 'note this down', 'don't forget', 'this is important', 'bookmark this', or when a significant decision, bug fix, architecture choice, or lesson learned occurs during a session. Also use after resolving tricky bugs, making technology choices, or discovering important patterns.Votes: 0GitHub stars: 73
- Cortex Setup ProjectBootstrap Cortex for a new project or import existing session history. Use when the user says 'set up Cortex', 'seed this project', 'import my history', 'backfill memories', 'bootstrap memory', 'initialize Cortex for this project', or when starting to use Cortex on an existing codebase that already has Claude Code conversation history.Votes: 0GitHub stars: 73
- Cortex Wiki AuthorAuthor first-class wiki pages (ADRs, specs, file docs, notes) that live alongside Cortex memory. Use when the user says 'this is an ADR', 'document this decision', 'write an ADR', 'add a spec', 'spec this out', 'document this file', 'add a note about', 'link these pages', 'bookmark this as a spec', or when finalizing a design decision that should persist as a human-readable document.Votes: 0GitHub stars: 73
- Evidence SynthesisSynthesize multiple papers, benchmarks, interviews, reviews, or other sources into a defensible and qualified conclusion. Use for conflicting evidence, literature synthesis, claim auditing, argument mapping, qualitative coding, belief updates, or any request that must expose counter-evidence, uncertainty, and source limitations.Votes: 0GitHub stars: 7
- Boundary DesignDraw the line where it costs least. Use for build-vs-buy calls, "where does this module/team/service boundary belong?", APIs and abstractions forcing users into implementation vocabulary, tools that should augment rather than automate, hardcoded decisions that belong at runtime, or information nobody can find.Votes: 0GitHub stars: 7
- Causal AuditCorrelation walked in; make it prove causation. Use when someone claims "X causes Y" from observational data, asks "did the change actually cause the improvement?", "is this confounded?", "what would have happened if we hadn't shipped it?", plans an A/B test, or investigates why an incident/outbreak spread the way it did.Votes: 0GitHub stars: 7
- Decision Bias CheckAudit the decision before it ships. Use for "are we sure about this?", high-stakes choices made on fast intuition, plans with no failure scenario, estimates that are suspiciously optimistic, metrics being gamed (Goodhart), unfalsifiable claims, negotiation prep, or strategies that break in extreme conditions.Votes: 0GitHub stars: 7
- EstimationBound it before you build it. Use when a decision is blocked by "we don't have data", an estimate looks suspiciously precise, someone asks "is this even feasible?", "how much capacity do we need?", "will this scale?", or a claimed number has never been cross-checked by a second method.Votes: 0GitHub stars: 7
- Experience And TransmissionThe artifact is correct and nobody can use, learn, or read it. Use when every component metric is green but the end-to-end experience is broken, when onboarding is too slow or documentation goes unread, when the observer is inside the system being studied (UX research, dogfooding), or when code is right but unreadable by the next maintainer.Votes: 0GitHub stars: 7
- Failure ForensicsRead the wreckage before rebuilding. Use for incident post-mortems, "what happens when everything goes wrong at once?", flaky or anomalous cases being filtered out as noise, "that's weird" moments nobody wrote down, oscillating or unstable feedback behavior, and designs whose only failure mode is crash.Votes: 0GitHub stars: 7
- Formal CorrectnessProve it, don't test-and-hope. Use for concurrent or distributed code with no written spec, "how do we know this is correct?", interfaces that break when implementations are swapped, correctness argued by walking through example traces, wall-clock time used for ordering, or "can this be decided at all?".Votes: 0GitHub stars: 7
- Measurement DisciplineFix the instrument before trusting the number. Use when someone says "the metric improved but I don't trust it", "measured more than the parts predict", "we want to improve X but nothing reads X", "the numbers don't add up", "requests/money/time are disappearing", or a measurement may perturb the system it measures.Votes: 0GitHub stars: 7
- Narrative SensemakingSome questions are "what happened and what did it mean", not "what is the mechanism". Use when an account must be reconstructed rather than measured, when a sequential process has a missing or out-of-order step, when a story is told to explain a failure, or when a claim sounds authoritative but may be structurally impossible before any source is even checked.Votes: 0GitHub stars: 7
- Normative DesignLegitimacy is a design property, not an afterthought. Use when a rule, policy, or allocation must be written or applied and the open question is "is this fair and consistently applied?" rather than "does it work", when a general rule does not determine a specific case, when harm emerged with nobody having decided it, or when "we've always done it this way" is the only justification on offer.Votes: 0GitHub stars: 7
- Problem ReframingThe question itself may be the bug. Use when a debate goes in circles, both options of a binary feel wrong, improving one parameter degrades another, "we're stuck" on a problem that resists direct attack, a metaphor is doing hidden work in the architecture, or a trade-off is being denied rather than made.Votes: 0GitHub stars: 7
- Representation And PossibilityWhen the notation is the obstacle and the option space was never enumerated. Use when the current vocabulary hides the solution, when a system claims to be exhaustive but nobody checked whether the space is searchable, when a forecast is too narrow because no one pushed the principle to its limit, or when you need the answer now and the proof afterwards.Votes: 0GitHub stars: 7
- Structure DiscoveryFind the hidden pattern that organizes the mess. Use for "these look related but we can't say how", classification with suspicious gaps, reverse-engineering an undocumented system or format, "is there a symmetry we're not using?", scale-free or fat-tailed data, or generating conjectures from computed special cases.Votes: 0GitHub stars: 7
- Systems LeverageFind where a small push changes the whole system. Use when local fixes keep failing, "where should we intervene?", recurring organizational patterns (shifting the burden, escalation, tragedy of the commons), behavior driven by stocks/flows/delays, adoption stalling, or shared resources being depleted.Votes: 0GitHub stars: 7
- Evidence SynthesisTurn a pile of sources into a defensible claim. Use for "what does the literature actually say?", conflicting studies or benchmarks, "is this result trustworthy?", arguments that need claim-evidence-warrant structure, qualitative data needing coding, or a theory with no catalog of its own contradicting evidence.Votes: 0GitHub stars: 7
- DesignUX/UI design and accessibility audit -- name the user, task, and success criterion before any layout decision, enforce WCAG 2.2 AA as a constraint from the first sketch, walk the 10 Nielsen heuristics, and refuse patterns that defeat usability or research integrity.Votes: 0GitHub stars: 7
- Advisor ModelConsult a separate model at a selected plan, fork, or completion decision while the current model retains execution ownership; use supplied context only, keep the consultation read-only, and never treat advice as a goal check.Votes: 0GitHub stars: 7
- GoalCompile a long-running objective into a persistent, host-neutral goal contract: one measurable end state, non-goals, acceptance criteria written as external checks with an expected exit code, a budget, and an iteration ledger. Mirrors the end state into the host''s native goal command so the host''s stop check and the contract agree.Votes: 0GitHub stars: 7
- PlanTurn an active goal contract into an ordered plan where every step carries its own check, then verify the plan against the goal before any code is written: each criterion is covered by at least one step, no step touches a non-goal, and the first step is the one that retires the most uncertainty.Votes: 0GitHub stars: 7
- Refine GoalAfter a verify-goal run, turn the ledger into the next iteration: tighten criteria that passed by accident, add the criterion a failure revealed was missing, write the backlog the next plan starts from, and record the lesson in the memory layer. Never widens the end state; a wider end state is a new goal.Votes: 0GitHub stars: 7
- Verify GoalRun every acceptance criterion of a goal file as an external check, record the command, its exit code and an output excerpt per criterion, and write a per-criterion verdict into the goal''s iteration ledger. Distinct from claim verification: this judges a deliverable against its contract, never a statement against its sources.Votes: 0GitHub stars: 7
- Impact AnalysisTrace the structural blast radius of a proposed or actual code change with ai-architect. Use for implementation planning, pull-request review, regression analysis, dependency checks, or identifying callers, importers, users, communities, and processes affected by a symbol or diff.Votes: 0GitHub stars: 6
- Understand CodebaseBuild an evidence-backed map of an unfamiliar repository with the ai-architect code graph. Use before implementing a feature, debugging an unfamiliar subsystem, explaining architecture, or making structural claims about symbols and dependencies.Votes: 0GitHub stars: 6
- Validate Change PlanCheck whether a proposed implementation plan matches the current code graph. Use before coding or approving a plan that names files, symbols, dependencies, boundaries, or expected blast radius; this is structural plan validation, not full PRD or semantic correctness verification.Votes: 0GitHub stars: 6
- Cortex VisualizeLaunch the interactive Cortex neural-graph visualization (the hypermnesia-mcp-viz MCP). Use when the user says 'show visualization', 'show me the graph', 'visualize memories', 'show memory map', 'open neural graph', 'cortex-visualize', or when a visual overview of the memory system, codebase graph, or session trace would help.Votes: 0GitHub stars: 4
- SkillAction-driven PRD generation. The MCP server runs a stateless 20-step pipeline reducer (11 PRD-generation steps + 9 opt-in implementation steps behind a human gate); the host (Claude Code) executes each substantive action and feeds the result back via submit_action_result, looping until done. Multi-judge verification combines genius reasoning patterns with zetetic team subagents. Grounded in the ai-architect ecosystem (ai-architect-mcp-codebase MCP, Cortex MCP, zetetic-team-subagents).Votes: 0GitHub stars: 4
- Audit PrdAudit a multi-section PRD with deterministic Hard Output Rules and cross-section consistency checks. Use when reviewing a complete product requirements document, checking FR-to-AC coverage, acceptance-criteria numbering, story-point arithmetic, or test traceability.Votes: 0GitHub stars: 4
- Validate SpecValidate one PRD or technical-specification section with deterministic Hard Output Rules. Use when checking a single overview, requirement set, user-story section, acceptance-criteria section, API specification, data model, security section, test plan, deployment plan, risk section, timeline, source-code section, or test-code section.Votes: 0GitHub stars: 4