Loading...
Loading...
Found 60 Skills
Project Guidelines Skill (Example)
Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices). L2 Worker in ln-100-documents-pipeline.
[Utilities] ⚡⚡⚡⚡ Bootstrap a new project automatically
Quickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.
Analyze project briefs to resolve architectural ambiguity before tech stack selection. Determines greenfield vs brownfield, platform constraints, integration requirements, scale expectations, and team context. Produces architecture-context.json for downstream skills.
Use when implementing features, writing fullstack code, shipping UI + API + DB changes, or any hands-on engineering work in TypeScript, Python, React, Next.js, FastAPI, or SQL
Perform initial analysis of a codebase - detect tech stack, directory structure, and completeness. This is Step 1 of the 6-step reverse engineering process that transforms incomplete applications into spec-driven codebases. Automatically detects programming languages, frameworks, architecture patterns, and generates comprehensive analysis-report.md. Use when starting reverse engineering on any codebase.
CVE vulnerability testing coordinator that identifies technology stacks, researches known vulnerabilities, and tests applications for exploitable CVEs using public exploits and proof-of-concept code.
Bence's code style, tech stack, and workflow conventions
GitHub Research Assistant. Use this skill when the user wants to analyze a GitHub repository. Analysis dimensions -- 1) Basic information; 2) Purpose, what it can be used for; 3) Tech stack, including frameworks, languages, algorithms, etc.; 4) Usage and examples; 5) Technical architecture and module analysis
Generate implementable architecture solutions based on business requirements and tech stacks, providing structured suggestions and tech stack selection optimization through a four-step process (information collection, requirement sorting, iterative improvement, solution output)
Review and modernize Agent OS product documentation to ensure quantifiable value propositions and workspace-hub standards compliance.