Deep Next.js security audit (13 to 16, App and Pages Router). Version advisories, proxy and middleware auth, Server Actions, Route Handlers, data exposure, caching, config. Read-only.
Skills in this repository
legioncodeinc/vibe-coding-tools - Page 7
SkillsMP has collected 302 skills from legioncodeinc/vibe-coding-tools. Open a skill to review its source and details.
legioncodeinc/vibe-coding-toolsShowing 40 of 302 collected skills.
Deep security audit for Node servers, Python, Go, Rust, Rails, PHP, Spring, and .NET, plus secrets, dependencies, SAST, and CI. Read-only, writes Audit My Code findings.
Read-only repo health audit: Wasp Nest setup, agent readiness, CI, tests, lint, lockfiles, secrets, governance. Writes contract-shaped foundation findings and measures. Never edits the repo.
Audit Lovable-built Supabase apps: RLS denials, role-differential reads, function gating, auth posture, bundle-forensics key/endpoint extraction, findings triage, reporting.
Read-only bloat audit of any repo. jscpd duplication, knip or language dead-code tools with a spot-check, cloc size, function and closure structure, split plans, banded verdict.
Orchestrates /audit-my-code. Five tiers (foundation, vibe, basic, full, mario) of codebase audits, dispatched to paired Drones and delivered as a Legion Code Inc. brief.
Render the Audit My Code brief, one self-contained Field Guide styled HTML file per run, from the workspace only. Escapes repo text, merges duplicates, prints cleanly to PDF.
Turn a validated opportunity into one bounded first-version PRD with measurable acceptance and deferred scope.
Test an app or business idea against customer evidence, current alternatives, and a falsifiable experiment.
Turn a solo or small-team development goal into a five-area responsibility map, a working queue, a Definition of Done, and a review rhythm.
Write and audit OKRs. Use for measurable key results, quarterly cadence, grading, or OKR-vs-KPI decisions. Read README.md for the guide map.
Facilitate engineering retrospectives. Use for format selection, safety pre-check, facilitation, or action-item follow-through. Read README.md for the guide map.
Explain software licenses and prepare artifact evidence for copyleft or commercial distribution review. Use for license literacy, notices, GPL or AGPL boundary questions.
Assess product assumptions, operational/security exposure and unresolved variables before a build decision.
Compare build, licensed vendor and partner approaches for one bounded functional slice using dated evidence and lifecycle responsibilities.
Forecast one person's AI-assisted software project at N hours daily, with learning, verification, external waits and separate cash/time scenarios.
Explain and inventory software license evidence, distribution boundaries and unresolved review questions without relabeling rights.
Improve Kanban flow. Use for WIP limits, cycle time, throughput, Little's Law, board design, or cumulative flow. Read guides/ for the decision path.
Draft SaaS legal documents with lawyer review. Use for Terms, Privacy Policy, DPA, MSA, cookie notice, or generator choice. Read guides/ for the decision path.
Choose payroll and EOR tools. Use for Gusto vs Rippling, contractor classification, international hiring, or benefits. Read guides/ for the decision path.
Set up a software company. Use for entity choice, Atlas vs Clerky, EIN, banking, bookkeeping, or founder paperwork. Read README.md for the guide map.
Manage startup cap tables and fundraising paperwork. Use for SAFEs, options, 409A, priced rounds, vesting, or data rooms. Read README.md for the guide map.
Forecast software delivery or an AI-assisted solo build at N hours daily. Use for sizing, NoEstimates, cycle-time data, or time/cash scenarios. Read README.md for the guide map.
Choose and configure an applicant tracking system. Use for pipeline stages, scorecards, calibration, sourcing, or ATS-to-HRIS handoff. Read README.md for the guide map.
Compare build, buy and partner approaches for one defined function using requirements, dated evidence, lifecycle costs, ownership and exit constraints.
Decide when to hire or buy services from demand, skill gaps, available hours, review capacity and dated quotes. Prepare one provisional staffing recommendation.
Run pre-build discovery: interviews, assumption tests, demand evidence, continue/pivot/stop decisions, and first-version scope. Read README.md for guides.
Coach Scrum teams. Use for ceremonies, roles, Definition of Done, estimation, or Scrum anti-patterns. Read guides/ for the decision path.
Playwright and Puppeteer automation for deterministic browser tests, debugging, downloads, screenshots, and browser lifecycle control. Use for browser automation work.
Chrome DevTools Protocol and Chromium development for remote debugging, profiles, protocol inspection, source builds, and browser-engine diagnosis. Use for Chrome or Chromium engineering.
Runs Lighthouse and PageSpeed Insights for React/Next.js: CI setup (LHCI), audit categories, performance budgets, lab-vs-CrUX gap. Use when setting up or debugging Lighthouse CI.
Capture a live web app. Demo video and script; component library with design tokens, a Claude Design handoff zip, and a shadcn/ui map; UI inconsistency audit. By Legion Code Inc.
Capture live web apps. Demo videos and scripts; component library with tokens, a Claude Design handoff zip, and a shadcn/ui map; visual and code audits.
Review TypeScript and Node code. Use for SvelteKit types, tsconfig, ESM, Zod boundaries, testing, or npm package builds. Read README.md for the guide map.
Tauri 2 engineering for desktop and mobile: updates, migration, IPC, capabilities, sidecars, AI runtimes, persistence, signing, updater, testing, and distribution. Use for Tauri-specific work.
Improve terminal workflows. Use for Bash, Zsh, Fish, modern CLI tools, dotfiles, tmux, or just/make automation. Read README.md for the guide map.
Rust development specialist for Cargo, async services, persistence, CLI/TUI, tests, upgrades, and current toolchains. Use for Rust implementation, review, migration, or release guidance.
Scope and build an authorized desktop-app slice with an explicit native boundary and native verification.
Build the server side of a mobile product with accepted identity, API compatibility and unreliable-network contracts.
Recommend one backend language/runtime from workload, integration, operations and actual implementation coverage.