- Skills
- 19
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
marynabieliaieva 的 Skills 19
workflow-retro
Retrospective of a finished multi-agent workflow run (e.g. /sdd-engineering:run-plan, a code review, spec → plan → execution) — collects run facts (agents spawned, spawn order and waves, tokens per agent and per type, fix rounds, caps hit, human interventions), extracts insights per agent type (what was hard, what was easy, what information was duplicated, what each gate missed and who caught it later) and turns them into concrete, evidence-backed proposals for agent/skill/plan changes. Writes a ledger entry to docs/retro/ledger/ and a summary in chat. Data source is the current conversation by default; --deep also parses the session transcripts on disk. Invoked only by the user as /sdd-engineering:workflow-retro — never automatically, never by another skill or agent.
run-plan
Runs the Spec Driven Development execution workflow for an already-written Implementation Plan (docs/plans/<slug>.md) — implementer tasks wave by wave along the plan's DAG, one plan-verifier pass with a fix loop, an architecture-review loop (review → fix → re-review until clean or the round cap), then one full test run. Accepts the plan, optionally the spec, extra requirements text and design files. Does NOT run spec-creator or implementation-planner (those are run manually first). Invoked only by the user as /sdd-engineering:run-plan.
engineering-insights
Captures a non-obvious engineering insight (a working pattern, an antipattern/dead end, a decision with its reason, or a recurring error and fix) found while working in this repo, and files it into the INSIGHTS.md of the package the session touched. Use at the end of a session that learned something substantial, or immediately when something surprising comes up — skip when nothing non-obvious happened.
flaky-patterns
Reference catalogue of flaky-test causes — for each class, how it shows up in a stack trace, the real fix, the masking fixes to reject, and how to reproduce it deterministically without running the test many times. Use when diagnosing or reviewing a fix for a test that passes and fails on the same code.
flaky-fix
Triage and fix one flaky test without extra pipeline or test runs — from the test name, a stack trace, the date it became flaky and its failure rate to a Jira issue, a fix branch, a reviewed commit and a PR, with verification left to the normal runs of main after merge. Invoked only by the user as /flaky-fix:flaky-fix.
zod
Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover form-library integration (e.g. React Hook Form resolvers) or OpenAPI client generation.
typescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
skill-routing
Decides which engineering-paved-path skills apply to a set of files or a task — for agents that write code (implementer, test writers, planners) and agents that review it. Reads the project's own file→skill map (.claude/skill-routing.md) when it exists, otherwise uses the default map in this skill. Use before writing or reviewing code to pick skills once per session instead of per file, and to decide digest (RULES.md) vs. full skill.
security
Web application security best practices based on OWASP Top 10:2025. Use when reviewing code for vulnerabilities, implementing auth/authorization, handling user input, working with file uploads, managing secrets, or building API endpoints. Covers React, Express, MongoDB, and JWT security.
react-testing-library
General-purpose React Testing Library guide with Vitest. Use when writing, reviewing, or setting up React component and hook tests. Covers project setup from scratch, RTL query priority, userEvent, async patterns, mocking strategies, and common anti-patterns. Applicable to any Vite + React project.
react-best-practices
Modern React best practices and anti-pattern catalog (2025-26). Use when writing, reviewing, or refactoring React components, hooks, and state management. Covers component design, state patterns, hooks misuse, performance, data fetching, and code organization.
pr-description
Writes a pull request description in a fixed shape — a generated change-stat line (Logic / Tests / Docs), then Summary, What changed, Validation and Test this branch, plus Why, topic sections, Review notes and Screenshots only when the change needs them. Use when the user asks to write, draft or update a PR description, PR body or merge request text for the current branch.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
onion-architecture
Enforces Onion/Layered Architecture for TypeScript backend modules — which direction dependencies are allowed to point, where domain types vs. I/O adapters vs. transport code must live, and how a new external integration must go through a port interface instead of a direct SDK import. Use this skill whenever scaffolding a new backend module, adding a new external integration (a new SDK, API client, or database access path), reviewing a PR that touches routes.ts/service.ts/ repository.ts, deciding whether code belongs in domain, application, or infrastructure, or wiring something into the DI container. Also use it when a service.ts or route handler is reaching for drizzle-orm, octokit, openai, or @anthropic-ai/sdk directly — that's the exact violation this skill exists to catch. Complements frontend-ui-architecture (the client-side counterpart skill) — that one governs where client code lives, this one governs the backend's dependency direction.
next-best-practices
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
mermaid-diagram
Create Mermaid diagrams in markdown. Use when the user wants to visualize workflows, architectures, API flows, data models, state machines, or system designs. Covers flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, and more.
frontend-ui-architecture
React + Next.js frontend architecture and code organization guide — where components, constants, utils/helpers, and business logic should live, how to split components, feature-based folder structure, colocation, and module boundaries. Use whenever deciding WHERE a new component, hook, constant, util, or business-logic function should go, when designing or reviewing a feature folder, or when a component/file is growing and needs to be split. This is about project structure and separation of concerns, not component internals, hooks correctness, or performance — for those use react-best-practices; for Next.js file conventions (routing, RSC, metadata) use next-best-practices.
fastify-best-practices
Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication, configuring CORS and security headers, integrating databases, working with WebSockets, and deploying to production. Covers the full Fastify request lifecycle (hooks, serialization, logging with Pino) and TypeScript integration via strip types. Trigger terms: Fastify, Node.js server, REST API, API routes, backend framework, fastify.config, server.ts, app.ts.