MrCipherSmith

@mrciphersmith source repo

103 skills
0 followers
9 hours ago last updated

▌
Job Documenter 2 · mrciphersmith bundle
Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/.

0
installs
▌
Job Orchestrator 2 · mrciphersmith bundle
Use when a GitHub issue or complex intent needs to be analyzed, planned, and implemented end-to-end with sub-agents.

0
installs
▌
Review Logic 2 · mrciphersmith
Use when: reviewing code for logic correctness, algorithmic bugs, missing error handling, async/await mistakes, null/undefined risks, race conditions, type contract violations, or spec compliance. Dispatched by review-orchestrator for --frontend, --backend, and --all. Also invoked directly: "review logic", "check correctness", "are there any bugs here". NOT for: security vulnerabilities, performance profiling, style/naming preferences, or architectural pattern concerns — those belong in their respective specialized reviewers.

0
installs
▌
Prd Creator 2 · mrciphersmith bundle
Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document.

0
installs
▌
Review Architecture 2 · mrciphersmith
Use when: reviewing code for architectural violations — layer violations, dependency direction mistakes, module boundary coupling, SOLID principle breaches, NestJS module/provider structure, React MVVM boundary violations, or MobX store layer misplacement. Triggered by: "review architecture", "check architecture", "architectural review", or dispatched by review-orchestrator with --architecture or --backend. NOT for: style/naming preferences, logic correctness bugs, or security vulnerabilities.

0
installs
▌
Review Orchestrator 2 · mrciphersmith bundle
Use when: a code review is requested and the user does not explicitly name a specialized reviewer. Handles "review", "code review", "review PR", "review --frontend", "review --backend", "review --architecture", "review --security", "review --performance", "review --style", "review --strict", "review --project-conventions", "review --legacy-profiles", "review --all". Routes to specialized reviewers in parallel and consolidates findings into one unified report. NOT for: running a single specialized reviewer — invoke it directly by name instead.

0
installs
▌
Pr Issue Documenter 2 · mrciphersmith bundle
Use when documenting PR changes, adding a PR description, creating a linked issue for a PR, or updating an existing issue body.

0
installs
▌
Job Documenter 3 · mrciphersmith bundle
Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/.

0
installs
▌
Feature Analyzer 2 · mrciphersmith bundle
Use when analyzing feature branch changes across repos, planning implementation, or understanding backend→frontend contracts. NEVER start without explicit user confirmation of source, target, and branch.

0
installs
▌
Job Orchestrator 3 · mrciphersmith bundle
Use when a GitHub issue or complex intent needs to be analyzed, planned, and implemented end-to-end with sub-agents.

0
installs
▌
Task Implementer 2 · mrciphersmith bundle
Use when implementing a single decomposed task from issue-analyzer end-to-end, or executing autonomous code changes from a JSON task object.

0
installs
▌
Context Collector 2 · mrciphersmith bundle
Use when a job needs a unified context document — gathering docs, libraries, and references for sub-agents before execution.

0
installs
▌
Pr · mrciphersmith bundle
Use when opening a pull request for the current branch.

0
installs
▌
Iago · mrciphersmith bundle
Use when generating or updating a Mermaid diagram for a GitHub pull request review, especially after reviewing a diff and needing to explain control flow, sequence, classes, or entity relationships. Triggered by: iago, /iago, /squawk, generate PR diagram, add Mermaid diagram to PR, or visualize this review.

0
installs
▌
Push · mrciphersmith bundle
Use when pushing the current branch to the remote, especially when upstream tracking or safety checks are needed.

0
installs
▌
Commit · mrciphersmith bundle
Use when committing code changes and a well-structured conventional commit message is needed, with optional amend or selective staging.

0
installs
▌
Deploy · mrciphersmith bundle
Use when deploying to any environment (staging, production) or when a deployment pipeline needs to run.

0
installs
▌
Hookify · mrciphersmith bundle
Use when adding automated hook behavior to Claude Code or Cursor from a natural language description.

0
installs
▌
Test Gen · mrciphersmith bundle
Use when unit or integration tests need to be written for a specific file or module.

0
installs
▌
Changelog · mrciphersmith bundle
Use when generating a changelog, release notes, or summarizing what changed between tags, versions, or date ranges.

0
installs
▌
Interview · mrciphersmith bundle
Use before implementation, design, or migration when requirements are unclear and targeted clarifying questions are needed to gather precise context.

0
installs
▌
Brainstorm · mrciphersmith bundle
Use when exploring architecture decisions, tech choices, feature ideas, or any open-ended problem that benefits from multiple perspectives.

0
installs
▌
DB Migrate · mrciphersmith bundle
Use when creating, applying, rolling back, or checking the status of database migrations.

0
installs
▌
Perf Check · mrciphersmith bundle
Use when measuring bundle size, detecting performance regressions, auditing slow queries, or investigating why something is slow.

0
installs
▌
Brd Creator · mrciphersmith bundle
Use when a user request needs to be transformed into a Business Requirements Document (BRD) capturing business context, stakeholders, and success metrics.

0
installs
▌
Code Review · mrciphersmith
Comprehensive code review with 4 parallel agents: correctness/logic, security, performance, style/maintainability. Produces unified severity report (CRITICAL/HIGH/MEDIUM/LOW). Use for thorough PR reviews and pre-merge checks.

0
installs
▌
Feature Dev · mrciphersmith bundle
Use when taking a feature from idea or GitHub issue all the way to a merge-ready PR in one guided workflow.

0
installs
▌
Fsd Creator · mrciphersmith bundle
Use when PRD and BRD exist and need to be expanded into a Functional Specification Document (FSD) detailing feature behavior, UI states, logic rules, and interface contracts.

0
installs
▌
Interviewer · mrciphersmith bundle
Use when requirements are ambiguous and precise clarification is needed before proceeding with a complex task.

0
installs
▌
Prd Creator · mrciphersmith bundle
Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document.

0
installs
▌
Trd Creator · mrciphersmith bundle
Use when PRD and FSD exist and need to be expanded into a Technical Requirements Document (TRD) covering architecture, tech stack, data models, API contracts, and non-functional requirements.

0
installs
▌
Caveman Mode · mrciphersmith
Use when the user wants all AI responses in the current session to be terse and token-efficient. Activates caveman-mode: no preamble, no filler, fragments over sentences, bullets over prose.

0
installs
▌
Review Logic · mrciphersmith
Use when: reviewing code for logic correctness, algorithmic bugs, missing error handling, async/await mistakes, null/undefined risks, race conditions, type contract violations, or spec compliance. Dispatched by review-orchestrator for --frontend, --backend, and --all. Also invoked directly: "review logic", "check correctness", "are there any bugs here". NOT for: security vulnerabilities, performance profiling, style/naming preferences, or architectural pattern concerns — those belong in their respective specialized reviewers.

0
installs
▌
Review Style · mrciphersmith
Use when: reviewing code for style, naming conventions, readability, and DRY violations — without touching logic, architecture, security, or performance. Covers "review style", "style review", "check naming", "check readability", or dispatched by review-orchestrator with --style flag. NOT for: logic bugs, architectural violations, security vulnerabilities, performance anti-patterns, or any finding that could cause a functional regression.

0
installs
▌
Code Verifier · mrciphersmith bundle
Use when running a full quality gate after implementation — lint, type-check, tests, and import validation. Mandatory step in job-orchestrator after task-implementer and after fix iterations. Use standalone when you need a structured verification report.

0
installs
▌
Review Strict · mrciphersmith
Use when: a strict engineering pass is needed — either as a meta-reviewer reading consolidated findings from other reviewers and elevating weak findings, or standalone on a git diff. Covers "strict review", "review --strict", "boss review", "review as boss", or dispatched by review-orchestrator as an optional post-pass after other reviewers complete. NOT for: first-pass review (run domain reviewers first); large refactors outside the diff scope (file separately).

0
installs
▌
Tests Creator · mrciphersmith bundle
Use when writing test cases BEFORE implementation — converts acceptance criteria into failing test stubs that task-implementer will make pass. Mandatory step in the TDD pipeline between issue-analyzer and task-implementer.

0
installs
▌
Autodoc Writer · mrciphersmith
Phase 4 subagent for autodoc-orchestrator. Writes one documentation section from analysis artifacts. Dispatched in parallel — one instance per section. Use when: dispatched by autodoc-orchestrator Phase 4. NOT for: direct user invocation.

0
installs
▌
Code AI Review · mrciphersmith bundle
Performs strict AI code review following code-review-ai-assistant.mdc standards. Reviews current branch changes from merge-base by default, including both committed and local uncommitted changes. Use when: code review requested, checking branch changes, reviewing implementation quality.

0
installs
▌
Issue Analyzer · mrciphersmith bundle
Use when decomposing a GitHub issue into atomic tasks for AI implementation, planning task breakdown, or preparing work for task-implementer agents.

0
installs
▌
Job Documenter · mrciphersmith bundle
Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/.

0
installs
▌
Review Backend · mrciphersmith
Use when: reviewing NestJS backend changes — API design, service layer, DTO validation, database patterns, and TypeScript correctness. Covers "review backend", "backend review", "review API", "review NestJS", or dispatched by review-orchestrator with --backend flag. NOT for: frontend patterns, MobX, React components, general security vulnerabilities (use review-security-code for XSS/injection/auth-bypass), or performance profiling (use review-performance).

0
installs
▌
Security Audit · mrciphersmith bundle
Use when checking for dependency vulnerabilities, accidentally committed secrets, or security issues in Docker images.

0
installs
▌
Autodoc Analyst · mrciphersmith
Phase 2 subagent for autodoc-orchestrator. Deep-dives into a single module to extract purpose, structure, public API surface, patterns, and key dependencies. Use when: dispatched by autodoc-orchestrator Phase 2 (one instance per module). NOT for: direct user invocation.

0
installs
▌
Autodoc Scanner · mrciphersmith
Phase 1 subagent for autodoc-orchestrator. Scans project structure, detects stack, identifies module boundaries, entry points, and dependencies. Use when: dispatched by autodoc-orchestrator Phase 1. NOT for: direct user invocation.

0
installs
▌
Plan Gatekeeper · mrciphersmith bundle
Relentless interactive plan gatekeeper. Stress-tests design choices, architecture, API contracts, state management, and edge cases. Proposes Architectural Decisions (ADR) in the final response status block.

0
installs
▌
Review Frontend · mrciphersmith
Use when a frontend review is requested, checking React component patterns, MobX state management (observer, actions, computed, reactions, lifecycle), View-Store boundaries, and TypeScript safety in changed frontend code. NOT for backend patterns, security vulnerabilities, performance bottlenecks, or cross-layer architecture.

0
installs
▌
Review Greptile · mrciphersmith
Use when: a PR needs codebase-aware review using Greptile — an AI reviewer with full repository indexing. Unlike diff-only reviewers, Greptile understands cross-file impact across the entire codebase. Triggered by: "greptile review", "review with greptile", "review --greptile", or dispatched by review-orchestrator on PRs. Requires: PR number + GitHub/GitLab repo name. NOT for: path-mode reviews or diff without a PR number — use other review-* skills instead.

0
installs
▌
Review Highload · mrciphersmith
Use when: reviewing code that will run under high concurrency or high traffic — race conditions, connection pool exhaustion, cache invalidation, missing indexes, unbounded queues, missing backpressure, retry storms, idempotency gaps, hot-path blocking I/O, and distributed systems anti-patterns. Triggered by: "review highload", "review scalability", "highload review", "review concurrency", "review --highload", or dispatched by review-orchestrator. NOT for: frontend re-render performance (review-performance), general N+1 queries (review-performance), clean code style (review-clean-code), or NestJS module structure (review-architecture).

0
installs
▌
Code Boss Review · mrciphersmith bundle
Performs strict boss-style code review following code-review-boss-profile.mdc. Reviews current branch changes from merge-base. Direct, no-fluff feedback focused on logic correctness. Use when: boss review requested, strict validation needed.

0
installs
▌
Feature Analyzer · mrciphersmith bundle
Use when analyzing feature branch changes across repos, planning implementation, or understanding backend→frontend contracts. NEVER start without explicit user confirmation of source, target, and branch.

0
installs
▌
Gproject Planner · mrciphersmith bundle
Generates roadmap, milestones, task breakdown, and dependency graph from PRD. Use when: dispatched by gproject-orchestrator Phase 6. NOT for: direct user invocation.

0
installs
▌
Job Orchestrator · mrciphersmith bundle
Use when a GitHub issue or complex intent needs to be analyzed, planned, and implemented end-to-end with sub-agents.

0
installs
▌
Task Implementer · mrciphersmith bundle
Use when implementing a single decomposed task from issue-analyzer end-to-end, or executing autonomous code changes from a JSON task object.

0
installs
▌
Flow · mrciphersmith bundle
Use whenever the user asks to start, create, track, or finish a managed piece of work - "создай фло", "заведи флоу из этой ишью", "create a flow", "start a story", "какой статус по фло", "заверши фло/стори", or pastes an issue link asking to work on it. All flow state changes go through the keryx flow CLI; never edit flow.json or frozen acceptance criteria by hand.

0
installs
▌
Autodoc Architect · mrciphersmith
Phase 3 subagent for autodoc-orchestrator. Synthesizes all module analyses into a system-level architecture description: layers, data flows, integration points, and cross-cutting concerns. Use when: dispatched by autodoc-orchestrator Phase 3. NOT for: direct user invocation.

0
installs
▌
Autodoc Assembler · mrciphersmith
Phase 5 subagent for autodoc-orchestrator. Assembles all documentation sections into a cohesive package: main README.md and navigation index. Use when: dispatched by autodoc-orchestrator Phase 5. NOT for: direct user invocation.

0
installs
▌
Code Style Review · mrciphersmith bundle
Detailed code style and architecture review using code-style-patterns.mdc. Reviews current branch changes. Checks naming, organization, patterns, TypeScript usage. Use when: style validation needed, architecture review.

0
installs
▌
Context Collector · mrciphersmith bundle
Use when a job needs a unified context document — gathering docs, libraries, and references for sub-agents before execution.

0
installs
▌
Dependency Update · mrciphersmith bundle
Use when checking for outdated packages or upgrading dependencies with compatibility verification.

0
installs
▌
Review Clean Code · mrciphersmith
Use when: reviewing code against Clean Code principles (Uncle Bob) and SOLID at the function/class level — meaningful names, small functions, single level of abstraction, argument count, error handling, DRY, comment quality, and SOLID (SRP, OCP, LSP, ISP, DIP) as applied to individual classes and functions. Triggered by: "review clean code", "check clean code", "Uncle Bob review", "SOLID review", "review --clean-code", or dispatched by review-orchestrator. NOT for: architectural layer violations (review-architecture), naming convention formatting (review-style), logic correctness bugs (review-logic), or security (review-security-code).

0
installs
▌
Review Flow Graph · mrciphersmith
Use when reviewing generic ReactFlow or graph-surface abstraction changes: public graph surface, store subclassing, layout lifecycle, internal helper boundaries, selection lifecycle, and large-graph performance. Dispatched by review-orchestrator for --flow-graph, --project-conventions, --all, or src/core/flow/** / graph abstraction changes.

0
installs
▌
Spec Orchestrator · mrciphersmith
Use when a user request needs to be converted into a full pre-implementation documentation suite (BRD → PRD → FSD → TRD) with iterative review at each document stage.

0
installs
▌
Gdctx · mrciphersmith
Use for commands, search, diff, test logs, lint/build output, and large file reads that can produce long output; prefer compact keryx ctx output before loading raw command output into agent context.

0
installs
▌
Gproject Discovery · mrciphersmith bundle
Collects and structures initial project information from multiple sources. Use when: dispatched by gproject-orchestrator Phase 0. NOT for: direct user invocation — always called through orchestrator.

0
installs
▌
Pr Review Comments · mrciphersmith
Собирает комментарии к указанному PR (по ссылке) через GitHub MCP или gh, группирует по авторам, при комментариях от boss предлагает обновить правило core/code-review-boss-profile.mdc (с согласия пользователя), анализирует каждый комментарий и даёт объяснение и возможный фикс. Триггеры: разбери комментарии к PR, комментарии к PR, pr review comments, обнови правило по ревью boss.

0
installs
▌
Review Performance · mrciphersmith
Use when a performance review is requested, checking for N+1 queries, unnecessary re-renders, memory leaks, missing indexes, large bundle imports, and synchronous blocking in changed code. NOT for security, logic correctness, style, or architecture.

0
installs
▌
Review Pr Feedback · mrciphersmith
Use when: a developer has received PR review comments and wants to understand them, act on them, or extract patterns from them. Covers "analyze PR comments", "review PR feedback", "what did reviewers say", "parse PR #N", "explain PR comments", or dispatched by review-orchestrator when a PR URL is provided. NOT for: reviewing code directly — this skill reads human or bot PR feedback and makes it actionable. To review code, use the domain review skills.

0
installs
▌
Gdwiki · mrciphersmith
Use FIRST for conceptual questions - how something works, why, architecture, domain models, business rules, user scenarios, auth and other flows, integrations, and known decisions. Read wiki/index.md, then use gdgraph to reach code.

0
installs
▌
Health · mrciphersmith
Use for code quality state - lint, type, test, coverage, dependency, and complexity health of the project, a module, or a file. Read the health report before claiming quality status or gate results.

0
installs
▌
Memory · mrciphersmith
Use for durable project knowledge - past decisions, constraints, known mistakes, lessons, and patterns. Search memory before planning or implementing to avoid repeating mistakes; propose durable entries after tasks.

0
installs
▌
Pr Issue Documenter · mrciphersmith bundle
Use when documenting PR changes, adding a PR description, creating a linked issue for a PR, or updating an existing issue body.

0
installs
▌
Review Architecture · mrciphersmith
Use when: reviewing code for architectural violations — layer violations, dependency direction mistakes, module boundary coupling, SOLID principle breaches, NestJS module/provider structure, React MVVM boundary violations, or MobX store layer misplacement. Triggered by: "review architecture", "check architecture", "architectural review", or dispatched by review-orchestrator with --architecture or --backend. NOT for: style/naming preferences, logic correctness bugs, or security vulnerabilities.

0
installs
▌
Review Orchestrator · mrciphersmith bundle
Use when: a code review is requested and the user does not explicitly name a specialized reviewer. Handles "review", "code review", "review PR", "review --frontend", "review --backend", "review --architecture", "review --security", "review --performance", "review --style", "review --strict", "review --project-conventions", "review --legacy-profiles", "review --all". Routes to specialized reviewers in parallel and consolidates findings into one unified report. NOT for: running a single specialized reviewer — invoke it directly by name instead.

0
installs
▌
Gdgraph · mrciphersmith
Use by default for project navigation and file discovery before broad raw search, especially when the user asks where something is, what files are related, what might be affected, or needs implementation, review, refactoring, debugging, architecture, dependency, module relationship, import cycle, or orphan-file context.

0
installs
▌
Testing · mrciphersmith
Use before creating, changing, debugging, or reviewing tests. Read testing context and normalized reports before raw test logs.

0
installs
▌
Autodoc Orchestrator · mrciphersmith bundle
Autonomous reverse-engineering documentation pipeline — scans an existing codebase and produces comprehensive developer documentation without user involvement after initial setup. Use when: "autodoc", "generate docs for my project", "document this codebase", "reverse engineer documentation", "create project documentation from code", "сгенерируй документацию проекта", "задокументируй кодовую базу", "автодок", "autodoc". Trigger on: user provides a repo path, asks to document existing code, wants onboarding docs, API reference, or architecture overview generated automatically. NOT for: writing new PRDs or planning new features (use gproject-orchestrator).

0
installs
▌
Claude Md Management · mrciphersmith bundle
Use when saving session learnings, coding patterns, conventions, or commands discovered during work into CLAUDE.md files.

0
installs
▌
Gproject Spec Writer · mrciphersmith bundle
Generates PRD or Implementation Plan constrained by decisions registry, architecture doc, and best practices. Does NOT invent new architectural decisions. Use when: dispatched by gproject-orchestrator Phase 4. NOT for: direct user invocation.

0
installs
▌
Review Security Code · mrciphersmith
Use when a code-level security review is requested, checking for injection vulnerabilities, auth gaps, insecure cryptography, secrets, and OWASP Top 10 patterns in changed code. NOT for infrastructure, deployment, or dependency audits.

0
installs
▌
Gproject Orchestrator · mrciphersmith bundle
Project documentation orchestrator — builds PRDs, specs, and implementation plans through a phased pipeline of specialized subagents. Use when: "Create project documentation", "Write PRD for...", "Plan project...", "Document how to implement...", "Spec out feature...", "Project planning", "gproject", "Создай документацию проекта", "Напиши PRD". Make sure to use this skill whenever the user mentions PRD, project planning, technical specification, implementation plan, feature spec, architecture document, project documentation, or wants to plan any software project from scratch or document a new feature in an existing codebase — even if they don't explicitly say "PRD" or "spec". Also trigger on: "how should I build...", "plan out...", "what's the best approach to build...", "document the approach for...", "create a roadmap for...", "spec this out", "write requirements for...". NOT for: code implementation (use job-orchestrator), code review (use code-review skills).

0
installs
▌
Code Mobx Store Review · mrciphersmith bundle
Targeted MobX store and state logic review. Checks store/actions/computed/reactions, async runInAction, state typing, View↔Store boundaries. Use when: reviewing MobX changes, state management validation.

0
installs
▌
Gproject Stack Advisor · mrciphersmith bundle
Determines project level (MVP/pet/startup/production) and recommends optimal technology stack with trade-off analysis. Use when: dispatched by gproject-orchestrator Phase 2. NOT for: direct user invocation.

0
installs
▌
Review Core Boundaries · mrciphersmith
Use when reviewing shared core/infrastructure module changes for dependency direction, feature-boundary leakage, abstraction stability, composition, and blast-radius risks. Dispatched by review-orchestrator for --core-boundaries, --project-conventions, --all, or src/core/** changes.

0
installs
▌
Gproject Problem Definer · mrciphersmith bundle
Defines core problems, goals, non-goals, and success metrics from discovery data. Use when: dispatched by gproject-orchestrator Phase 1. NOT for: direct user invocation.

0
installs
▌
Review Testing Practices · mrciphersmith
Use when reviewing unit, integration, Storybook, component, or e2e tests against repository-local testing conventions: co-location, network mocking, MSW-style boundary mocks, behaviour assertions, deterministic waits, smoke/full split, locator priority, and screenshot-test discipline. Dispatched by review-orchestrator for --testing-practices, --project-conventions, --all, or changed test/e2e/story files.

0
installs
▌
Review Frontend Conventions · mrciphersmith
Use when reviewing frontend code against repository-local conventions commonly captured in CLAUDE.md or similar project guides: React/MobX boundaries, TypeScript strictness, i18n placement, storage wrappers, error handling, styling tokens, Storybook expectations, and local tooling rules. Dispatched by review-orchestrator for --frontend-conventions, --project-conventions, --all, or frontend src/**/*.ts(x) changes when local convention docs exist.

0
installs
▌
Gproject Consistency Checker · mrciphersmith bundle
Validates PRD/Implementation Plan against decisions registry, architecture doc, and best practices constraints. Catches contradictions, gaps, and violations. Use when: dispatched by gproject-orchestrator Phase 5. NOT for: direct user invocation.

0
installs
▌
Gproject Patterns Researcher · mrciphersmith bundle
Researches best practices per technology in the chosen stack and defines application architecture patterns. Produces constraints that PRD must follow. Use when: dispatched by gproject-orchestrator Phase 3. NOT for: direct user invocation.

0
installs
▌
Context Router · mrciphersmith
Use when choose between gdgraph, gdctx, gdwiki, memory, health, and project-skills before raw file reads.

0
installs
▌
Hook Manager · mrciphersmith
Use when create and verify lightweight git hooks for graph, health, and skill verification.

0
installs
▌
Metaproject Router · mrciphersmith
Use when choose which Metaproject module, working skill, or project-skill should be used for a user request.

0
installs
▌
Docpack Review · mrciphersmith bundle
Use when reviewing or verifying a Metaproject requirements package under docs/requirements for completeness, versioning, README/PRD/spec consistency, schema references, roadmap updates, unsupported claims, and implementation-status accuracy. Usually dispatched by docpack-orchestrator. Not for reviewing autodoc-generated current-codebase documentation.

0
installs
▌
Entity Skill Router · mrciphersmith
Use when select relevant project-skills for known modules, components, stores, services, and domain entities.

0
installs
▌
Entity Skill Creator · mrciphersmith
Use when create canonical project-skills from a path, symbol, wiki page, module, component, store, service, or domain entity.

0
installs
▌
Entity Skill Learner · mrciphersmith
Use when update project-skills from review findings, test failures, health reports, memory entries, and verifier reports.

0
installs
▌
Entity Skill Verifier · mrciphersmith
Use when verify project-skills against current code, graph, wiki, health, memory, tests, and review lessons.

0
installs
▌
Metaproject Security · mrciphersmith
Use when working with Metaproject Security: checking prompts, external content, memory/wiki/report writes, PII/secrets redaction, prompt-injection risk, data exfiltration, or security policy reports under .metaproject/security and .metaproject/data/security.

0
installs
▌
Docpack Orchestrator · mrciphersmith bundle
Use when creating or updating a Metaproject requirements package under docs/requirements: PRD, specification, README, policies/protocols/schemas, roadmap updates, verification, and package review. Use for requests like 'create requirements package', 'prepare module documentation', 'write PRD/spec for module', or 'оформи пакет документации'. Not for reverse-engineering current codebase documentation; use autodoc-orchestrator for that.

0
installs
▌
Skill Catalog Manager · mrciphersmith
Use when generate `.metaproject/skills/catalog.md` and machine-readable skill registry.

0
installs

103 published skills · page 1 of 2