project▌

Generates a fully configured Spring Boot project from scratch using the Spring Initializr API. The skill walks the user through selecting project parameters, choosing an architecture style (DDD or Layered), configuring data stores, and setting up Docker Compose for local development. The result is a build-ready project with standardized structure, dependency management, and configuration.

Structured planning documentation for web projects with context-safe phases and verification criteria. \n \n Generates IMPLEMENTATION_PHASES.md (always) plus conditional docs like DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, and CRITICAL_WORKFLOWS.md based on project complexity \n Phases sized for single 2-4 hour sessions with ≤8 files, clear task lists, and specific verification checkpoints (HTTP status codes, form validation, CRUD operations) \n Asks 3-5 clarifying questions upfront

Complete project architecture guide for LobeHub, an open-source AI Agent Workspace built on Next.js and React. \n \n Monorepo structure with @lobechat/ namespace packages covering agent runtime, model providers, database, tools, and platform-specific bridges (Electron, web, mobile) \n Tech stack includes Next.js 16, React 19, TypeScript, Zustand for state, tRPC for type-safe APIs, Neon PostgreSQL with Drizzle ORM, and antd-style for CSS-in-JS \n Three deployment targets: web (desktop/mobile), El

Deterministic WordPress repository inspection with structured JSON output for workflow guidance. \n \n Detects project kind (plugin, theme, block theme, WP core, Gutenberg, full site) and outputs a schema-validated JSON report including tooling, tests, and version hints \n Runs via Node.js detector script at repo root; outputs project.kind , signals , and tooling fields to guide downstream workflows \n Identifies PHP/Node tooling presence and test frameworks to inform which commands and conventi

Comprehensive project setup, auditing, and configuration management for Claude Code environments. \n \n Detects project type from file indicators (Node.js, Python, Rust, Go, Docker, Cloudflare, etc.) and auto-generates .claude/settings.local.json , CLAUDE.md , and .gitignore with appropriate permission presets \n Audits existing projects via parallel sub-agents: Permission Auditor scans for leaked secrets, stale MCP servers, permission gaps, and legacy syntax; Context Auditor checks CLAUDE.md qu

Run a read-only scan over repositories in a workspace root and rank cleanup chores by severity.

Search and extract HTTP traffic, audit findings, and security data from Burp Suite project files via CLI. \n \n Queries proxy history, site map, and audit items using regex patterns on request/response headers and bodies \n Requires Burp Suite Professional and the burpsuite-project-file-parser extension; delegates parsing to Burp's Java runtime \n Enforces sub-component filters (headers, bodies) instead of full dumps to prevent gigabyte-scale data retrieval; mandatory truncation of body content

psm is the compatibility alias for this canonical skill entrypoint.

Clear module boundaries, explicit public interfaces, and maintainable directory layouts for Python projects. \n \n Define public APIs with __all__ in every module; unlisted members remain internal implementation details \n Prefer flat directory structures with minimal nesting; add sub-packages only for genuine sub-domains \n Organize by architectural layers (API, services, repositories, models) or business domains depending on project complexity \n Keep files focused on a single concept; conside

Generates detailed implementation blueprints by analyzing project architecture, technology stacks, and workflow patterns. \n \n Auto-detects project type, entry points, persistence mechanisms, and architecture patterns (.NET, Java/Spring, React, microservices, etc.) to tailor documentation \n Documents complete end-to-end workflows across entry points, service layers, data access, error handling, and response construction with actual code examples \n Configurable output detail levels, workflow c