发现 Skills

Convert a contract PDF to clean markdown for clause extraction or LLM analysis.

Performs a comprehensive pre-production deployment check. Use before deploy, release, or reflecting changes to production. Runs combined verification of build, tests, security, and performance. Triggered by keywords like "deploy", "release", or "production".

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

Metric drops diagnosis with rigorous stepwise decomposition. Use when the user needs a product workflow for business analysis related to metric drops diagnosis with rigorous stepwise decomposition. Trigger terms: pm, business-analysis, analytics, metrics, diagnosis.

Multiple interface descriptions from a single image. Use when the user needs a product workflow for design & prototyping related to multiple interface descriptions from a single image. Trigger terms: pm, ux, design, communication, perspectives.

Pyramid-structure optimization from complex text. Use when the user needs a product workflow for presentation and communication related to converting complex text into a pyramid structure. Trigger terms: writing, storytelling, presentations, structured-thinking.

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.

Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use proactively for .NET API development, code review, or architecture decisions.

Backend-specialised design skill in the SSDAM pipeline. Reads architecture-design (and optionally schema-design) to produce a DDD-structured backend specification per domain. Mandatory components per domain are domain/entity, domain/facade, api/controller, and service/store. All other sub-layers (vo, event, exception, shared, request, response, mapper, proxy, config, application service) are optional and included only when needed.

Executar o papel 'QA Tela' na esteira IT Valley com base no prompt oficial do agente 13.

j10c's personal frontend coding playbook. Invoke only when the user explicitly asks for it — NEVER auto-trigger.

INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents. Covers required packages, minimum versions, environment requirements, versioning best practices, and common community tool packages for both Python and TypeScript.

INVOKE THIS SKILL when your LangGraph needs to remember state across calls, use memory, or persist conversations. Covers checkpointers (MemorySaver, Postgres), thread_id configuration, and Store for long-term memory.

AI-powered git commit message generation. Uses an LLM to summarize changes and create meaningful commit messages. Triggers when the user wants to commit changes, amend/squash commits, or needs the LLM to summarize changes for commit messages. Chinese triggers: 提交, 提交代码, 提交更改, 提交修改, 要提交, commit, 提交信息, git 提交, 生成提交信息.

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns. Keywords: Tailwind v4, shadcn/ui, @tailwindcss/vite, @theme inline, dark mode, CSS variables, hsl() wrapper, components.json, React theming, theme switching, colors not working, variables broken, theme not applying, @plugin directive, typography plugin, forms plugin, prose class, @tailwindcss/typography, @tailwindcss/forms

Use when reasoning about tests that specify universal properties of code rather than specific input-output pairs: the forall(input) → property quantification, the generator/shrinker primitives that produce inputs and minimize failing cases, the four-rules-of-simple-design analog (commutativity, associativity, idempotence, round-trip, oracle, invariant), the difference between example-based tests (one input, one assertion) and property-based tests (many generated inputs, one universal claim), why property tests find bugs example tests don't, the shrinking discipline that produces minimal failing cases, and the trade-off between generator complexity and bug-finding capacity. Do NOT use for specifying one concrete behavior with one input (use example-based tests under testing-strategy), for fuzz-testing focused on crashes (use fuzz-testing), for mutation testing as a test-suite quality signal (use mutation-testing), or for model-based testing of state machines (use state-machine-modeling).

Use when diagnosing whether a business has, can build, or is falsely claiming durable strategic power using Hamilton Helmer's Seven Powers: scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, and process power. Do NOT use for industry-structure analysis alone (use porters-five-forces), integrated strategy-cascade formulation (use playing-to-win), generic prioritization, or surface-level SWOT lists. Covers power as benefit plus barrier, moat-source classification, power progression by company phase, false-positive checks, and strategy implications. Do NOT use for analyze the attractiveness of this industry using entrants, suppliers, buyers, substitutes, and rivalry. Do NOT use for turn this market-entry plan into a winning aspiration, where to play, how to win, capabilities, and systems. Do NOT use for rank these roadmap items by impact and effort. Do NOT use for make a SWOT table for this company.

Use when routing an agent request across multiple Skills, building or auditing a routing table, detecting routing coverage gaps, or answering questions like "which Skill handles this?", "who routes X?", or "why did Skill A activate instead of B?". Covers trigger-label matching, file-path matching, keyword matching, description-based semantic matching, scope/type tiebreakers, and coverage-gap detection. Do NOT use when the target Skill is already known (load it directly), when authoring a new Skill (use `skill-metadata-template` instead), or when evaluating a SINGLE Skill's quality (use `graph-audit`).

Use when condensing prose while preserving meaning: session findings, wrap reports, research briefs, executive summaries, TLDRs, agent handoffs, progressive summaries, audit summaries, and long-document distillation. Covers extractive vs abstractive summarization, what to keep vs drop, evidence preservation, summary levels, handoff summaries, and audit-report condensation without hiding findings. Do NOT use for byte/data compression algorithms (use `compression`), context-window budget math or compaction triggers (use `context-window`), working-set selection (use `context-management`), prose tone repair (use `writing-humanizer`), or quality scoring (use `evaluation`).

설치 가능한 스킬을 검색하고 설치하는 스킬입니다. "X를 어떻게 해?", "X 스킬 찾아줘", "이런 기능 있어?" 같이 새로운 기능을 찾거나 확장하고 싶을 때 사용하세요.

Track AI code contributions for auditing and attribution. Use this skill BEFORE writing, editing, creating, or modifying any code files. Enables automatic detection of AI-authored vs human-authored code changes. Required for code attribution compliance.

List and manage pending approval requests for sensitive actions like emails, social posts, and payments. Use when a user asks to see pending approvals, wants to approve or reject actions, check what's waiting for approval, or manage the approval queue.

Use when reviewing learnings and journal entries to identify improvement opportunities across skills, documentation, and processes