Validate, format, and fix JSON data. Use this skill when working with JSON files, API responses, or configuration files that need validation or formatting.

Score and filter topics for X content creation using weighted criteria. Use when user wants to evaluate collected materials, filter topics by score, or mentions "filter topics", "score materials", "x-filter", "选题筛选". Applies 10-point scoring system with customizable weights.

仕様駆動開発（SDD）の**上流工程**を担当するSkill。

Autonomous multi-agent workflow system for complex coding tasks. Use when the user requests non-trivial changes that would benefit from autonomous execution with built-in review gates. Ideal for refactoring modules, adding major features, migrating codebases, adding comprehensive test coverage, or any multi-step development task that can run autonomously. NOT for simple fixes, typos, or single-file changes.

Use when reviewing UI diffs, accessibility audits, or flaky UI tests to catch a11y regressions, semantic issues, keyboard/focus problems, and to recommend minimal fixes plus role-based test selectors.

Use this skill at the START of every session. This is MANDATORY for quota management. location: plugin token_budget: 300. Use when session starts (mandatory), prompt sizes spike, tool calls increase, before long-running analyses or massive context loads. Do not use when context-optimization already handles the scenario. DO NOT use when: simple queries with minimal context.

Provides KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity, preventing over-engineering, and improving maintainability.

Functional Core, Imperative Shell: isolate deterministic logic from side effects for testability. Triggers: functional-core, imperative-shell, pure functions, side-effects, testability Use when: business logic is entangled with I/O or tests are brittle DO NOT use when: simple scripting without complex logic, or performance-critical hot paths where immutability overhead matters.

Single deployable with enforced module boundaries for team autonomy without distributed complexity. Triggers: modular-monolith, module boundaries, single deployment, team autonomy Use when: teams need autonomy without distributed overhead DO NOT use when: already using microservices or system is small.

Consult this skill when designing client-server systems or API architectures. Use when traditional web/mobile applications with centralized services, clear separation between client and server responsibilities needed. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.

Data-grid architecture for high-traffic stateful workloads with linear scalability. space-based, data grid, in-memory, linear scaling, high traffic Use when: traffic overwhelms database nodes or linear scalability needed DO NOT use when: data does not fit in memory or simpler caching suffices.

Asynchronous event-based communication to decouple producers/consumers for scalability and resilience. Triggers: event-driven, message queue, pub/sub, asynchronous, decoupling Use when: real-time workloads or multiple subsystems react to same events DO NOT use when: selecting paradigms (use architecture-paradigms first), simple request-response.

Coarse-grained service architecture for deployment independence without microservices complexity. service-based, SOA, coarse-grained services, domain services Use when: teams need deployment independence without microservices complexity DO NOT use when: fine-grained scaling needed - use microservices.

Consult this skill when designing data pipelines or transformation workflows. Use when data flows through fixed sequence of transformations, stages can be independently developed and tested, parallel processing of stages is beneficial. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: data flow is not sequential or predictable. DO NOT use when: complex branching/merging logic dominates.

Decouple domain logic from infrastructure using Hexagonal (Ports & Adapters) pattern. Triggers: hexagonal, ports-adapters, infrastructure-independence, domain-isolation, testability Use when: business logic separation, infrastructure changes needed, testability critical DO NOT use when: selecting paradigms (use architecture-paradigms first), simple CRUD.

Multi-LLM deliberation for strategic decisions via expert pressure-testing and consensus building. Use for critical, irreversible, or high-stakes architecture choices and conflicts. Skip for trivial or reversible decisions.

Serverless FaaS for event-driven workloads with minimal infrastructure management. serverless, FaaS, Lambda, event-driven, pay-per-use Use when: workloads are event-driven with bursty traffic DO NOT use when: long-running processes or stateful operations required.

Retrospective workflow evaluation and improvement of skills, agents, commands, and hooks. workflow improvement, retrospective, workflow efficiency Use when: workflow felt slow, confusing, or needs optimization DO NOT use when: simple one-off fixes - use fix-pr or do-issue instead.

Minimal core system with plugin-based feature extensibility for platform development. Triggers: microkernel, plugin-architecture, extensibility, platform-design Use when: platforms/IDEs/marketplaces, core stability critical, plugin isolation needed DO NOT use when: selecting paradigms (use architecture-paradigms first), no extensibility needed.

Consult this skill when designing permanent memory palace structures. Use when creating new memory palace structures, organizing complex domains, designing spatial layouts for knowledge retention. Do not use when quick knowledge search - use knowledge-locator instead. DO NOT use when: session-specific context - use session-palace-builder.