aiskillstore/marketplace - Page 17

systematic-debugging

Four-phase root cause investigation before attempting fixes. Use when debugging bugs, test failures, or unexpected behavior.

test-driven-development

Enforce RED-GREEN-REFACTOR cycle. Use when implementing features, fixing bugs, or writing any production code.

ultrathink-trigger

Auto-escalate reasoning depth for complex problems. Use proactively when encountering architecture, debugging, or unfamiliar code.

writing-plans

Create detailed implementation plans with granular tasks. Use before implementing features or complex changes.

agentdb-persistent-memory-patterns

Implement persistent memory patterns for AI agents using AgentDB - session memory, long-term storage, pattern learning, and context management for stateful agents, chat systems, and intelligent assistants

agentdb-semantic-vector-search

Build semantic vector search systems with AgentDB for intelligent document retrieval, RAG applications, and knowledge bases using embedding-based similarity matching

reasoningbank-adaptive-learning-with-agentdb

Implement ReasoningBank adaptive learning with AgentDB for trajectory tracking, verdict judgment, memory distillation, and pattern recognition to build self-learning agents that improve decision-making through experience.

when-gathering-requirements-use-interactive-planner

Use Claude Code's AskUserQuestion tool to gather comprehensive requirements through structured multi-select questions.

when-using-flow-nexus-platform-use-flow-nexus-platform

Comprehensive Flow Nexus platform management covering authentication, sandboxes, storage, databases, app deployment, payments, and monitoring. This SOP provides end-to-end platform operations.

clean-code

Clean code principles adapted for TypeScript-first, functional development.

codebase-analysis

Techniques for analyzing existing codebases to reverse-engineer requirements and understand business logic. Use when conducting brownfield analysis or understanding existing system capabilities.

cqs-patterns

Command Query Separation (CQS) and CQRS patterns for .NET. Use when designing methods, handlers, and application architecture. Ensures predictable, testable code.

functional-patterns

Functional programming patterns that promote testability, composability, and maintainability.

requirements-elicitation

Requirements gathering and elicitation techniques for business analysis. Use when conducting stakeholder interviews, gathering functional/non-functional requirements, or identifying gaps in requirements.

solid-principles

SOLID principles adapted for functional and TypeScript-first development.

tdd-workflow

Test-Driven Development methodology for Node.js/TypeScript projects.

technical-analysis

Technical analysis capabilities for APIs, data models, integrations, and security requirements. Use when analyzing technical aspects of systems or documenting technical requirements.

code-review

Complete code review workflow for both requesting and receiving reviews. Use when creating PRs, reviewing code, or responding to feedback.

Source text: Korean

d3-viz

Create interactive data visualizations using D3.js. Use this when creating charts, graphs, network diagrams, geographic visualizations, or custom SVG-based data visualization.

Source text: Mixed languages

error-handling

Enforce proper error handling patterns. Use when writing async code, API calls, or user-facing features. Covers try-catch, error boundaries, graceful degradation, and user feedback.

Source text: Korean

executing-plans

Execute plan in batches with review checkpoints. Use when partner provides a complete implementation plan to execute with controlled batches and architect review between batches.

Source text: Mixed languages

line-limit

Enforce file line count limits (200 recommended, 300 max) for CODE IMPLEMENTATION files only. Use this when reviewing code, creating files, or when files exceed line limits and need modularization.

Source text: Korean

mcp-builder

Guide for creating MCP (Model Context Protocol) servers. Use this when building integrations with external services, creating new MCP servers, or connecting Claude to APIs.

Source text: Mixed languages

no-hardcoding

Forbid hardcoded values in code. Use this when reviewing code, writing new features, or when magic numbers/strings are detected. Enforces constants, env variables, and config files.

Source text: Mixed languages

planning

Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.

Source text: Mixed languages

readme-for-developers

Write developer-oriented README as onboarding documentation. Use when creating/updating README, setting up new projects, or when new developers need to understand the codebase quickly. README = Entry point + Architecture overview + Working agreement.

Source text: Korean

report-writing

작업 완료 후 상세 리포트 문서를 작성. 변경 이력, 영향도 분석, 검증 결과를 문서화할 때 사용. 파일명 규칙 YYYY-MM-DD-<제목>-report.md

Source text: Korean

software-architecture

Clean Architecture and SOLID principles guide. Use this when designing systems, reviewing architecture, or making structural decisions.

Source text: Korean

structured-logging

Implement JSON-based structured logging for observability. Use when setting up logging, debugging production issues, or preparing for log aggregation (ELK, Datadog). Covers log levels, context, and best practices.

Source text: Korean

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent for each task with code review between tasks.

Source text: Mixed languages

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Four-phase framework ensuring understanding before attempting solutions.

Source text: Mixed languages

testing-strategy

Comprehensive testing workflow combining TDD, real implementations (no mocking), and E2E testing. Use when implementing features, writing tests, or setting up test infrastructure.

Source text: Mixed languages

triforce-sync-check

Verify 3-Mirror skill sync consistency across .public/skills, .codex/skills, and .claude/skills. Use after skill changes, before commits, or for CI validation.

Source text: Korean

typescript-strict

Enforce TypeScript strict mode and type safety. Use when setting up projects, reviewing code, or when type errors are ignored. Covers strict flags, no-any rules, and type inference best practices.

Source text: Korean

workhub

工作文档枢纽，强制执行 SSOT（Single Source of Truth）原则，管理 `docs/` 目录下的架构决策、设计文档、Issues（任务规划）、PRs（变更记录）。支持 GitHub 协作开发模式。

Source text: Chinese

ambiguous-question-guide

判断政务服务问题是否模糊，识别缺失要素（主语、证照名称、具体环节），生成精准的政务服务引导语。当用户提出不完整的办事问题或需要引导用户提供更多信息时使用。

Source text: Chinese

blog-writer

Write and add new blog posts for this Next.js site by matching the existing BlogPost structure in `src/lib/blog-data.ts`. Use when asked to draft a new blog article, update blog content, or produce SEO metadata/slug/image details for a new post.

receipt-scanner-master

Master receipt scanning operations including parsing, debugging, enhancing accuracy, and database integration. Use when working with receipts, images, OCR issues, expense categorization, or troubleshooting receipt uploads.

voice-agent-expert

This skill is a practical, 'use-it-while-debugging' reference for getting a LiveKit + Letta voice agent working reliably.

frontend-components

Design and build reusable, composable UI components following single responsibility principle with clear props, proper encapsulation, and minimal state management. Use this skill when creating or modifying React, Vue, Svelte, or web components, defining…