mcpField
L
ln-750-commands-generator

ln-750-commands-generator

github.com/levnikolaevichAgent workflows58481 installsUpdated 2d ago
Repository

About ln-750-commands-generator

A skill that analyzes a project’s structure and technology stack, then generates project-specific Claude Code commands. It is intended for project setup and delegates template rendering to ln-751-command-templates.

Key features

  1. 01Detects project structure and stack
  2. 02Extracts paths, ports, and frameworks
  3. 03Generates context and build commands
  4. 04Adds conditional UI, deployment, and database commands
  5. 05Verifies generated command files

Use cases

  1. 01Creating setup commands for a new project
  2. 02Preparing project-specific build and test workflows
  3. 03Generating UI test commands when Playwright is detected
  4. 04Adding deployment or database commands when relevant configuration exists

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-750-commands-generator

After installing, type/ln-750-commands-generatorin Claude Code to confirm it loaded.

Bundled filesreferences/questions_commands.mdreferences/variables_reference.md

Details

From the project README

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

ln-750-commands-generator

Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap

Generates .claude/commands/ with project-specific Claude Code commands.

Overview

AspectDetails
InputProject structure, tech stack
Output.claude/commands/*.md files
Workerln-751-command-templates

Workflow

  1. Analyze project structure and detect tech stack
  2. Extract variables (paths, ports, frameworks)
  3. Delegate to ln-751 with template name and variables
  4. Verify generated commands exist

Generated Commands

CommandPurposeCondition
refresh_context.mdRestore project contextAlways
refresh_infrastructure.mdRestart servicesAlways
build-and-test.mdFull verificationAlways
ui-testing.mdUI tests with PlaywrightIf Playwright detected
deploy.mdDeployment workflowIf CI/CD config exists
database-ops.mdDatabase operationsIf database detected

Variables Extracted

VariableSourceExample
{{PROJECT_NAME}}package.json / .csproj"my-app"
{{TECH_STACK}}Auto-detected"React + .NET + PostgreSQL"
{{FRONTEND_ROOT}}Directory scan"src/frontend"
{{BACKEND_ROOT}}Directory scan"src/MyApp.Api"
{{FRONTEND_PORT}}vite.config / package.json"3000"
{{BACKEND_PORT}}launchSettings.json"5000"

Templates and full variable list: see ln-751-command-templates/references/

Detection Logic

Frontend: vite.config.ts, package.json (react/vue/angular) Backend: *.csproj with Web SDK, or express/fastapi in deps Database: docker-compose.yml postgres/mysql, or connection strings Playwright: playwright.config.ts or @playwright/test in deps CI/CD: .github/workflows/, azure-pipelines.yml, Dockerfile

Critical Rules

  • Detect before generate: Only create commands for detected stack components (no empty templates)
  • Variable completeness: All {{VARIABLE}} placeholders must be resolved before delegation
  • Delegate via Task: All template rendering goes through ln-751 with context isolation
  • No hardcoded paths: All paths derived from project structure analysis, not assumptions

Definition of Done

  • Project structure analyzed and tech stack detected
  • Variables extracted (project name, ports, roots, stack)
  • Commands delegated to ln-751 with correct template name and variables
  • All generated .claude/commands/*.md files verified to exist
  • No unresolved {{VARIABLE}} placeholders remain in output

Reference Files

Version: 2.0.0 Last Updated: 2026-01-10

Comments

Markdown supported