project▌

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

Project-specific architecture, code patterns, and deployment guidelines for Zenith application. \n \n Next.js 15 frontend with FastAPI backend, Supabase PostgreSQL database, and Claude API integration via structured output \n Includes standardized API response formats, custom React hooks, and Pydantic models for type safety across stack \n Testing requirements: pytest with 80% coverage minimum for backend, React Testing Library for frontend, Playwright for E2E \n Deployment via Google Cloud Run

Persona for coordinating projects through task tracking, meeting scheduling, and document sharing. \n \n Requires five Google Workspace utility skills: Drive, Sheets, Calendar, Gmail, and Chat for full functionality \n Includes three built-in workflows: standup reports, weekly digests, and file announcements for common project coordination tasks \n Tracks project status by appending updates to Sheets, scheduling recurring team standups, and sending stakeholder emails \n Supports file discovery v

Use this flow to connect an existing repo to Eve and get the first deploy running.

When the user wants to create a new project, first infer as many options as possible from the user's request (e.g., "new Mojo project" means type=Mojo, "called foo" means name=foo). Then use a structured multiple-choice prompt (not plain text) to gather only the remaining unspecified options in a single interaction. Do NOT ask about options the user has already provided or implied. The options to determine are:

ln-112-project-core-creator

Creates a compilable, empty xUnit test project with transaction management and seed data infrastructure for a single target project. Run once per project before writing tests.