How do I install the Ln 750 Commands Generator skill?

Run npx skillmds@latest add majiayu000/ln-750-commands-generator-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ln 750 Commands Generator skill do?

Generates project-specific .claude/commands for Claude Code It is listed under Coding & Dev Tools on SkillMD.

Is Ln 750 Commands Generator safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ln 750 Commands Generator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ln 750 Commands Generator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ln 750 Commands Generator?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ln 750 Commands Generator by majiayu000

Name: Ln 750 Commands Generator
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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

Aspect	Details
Input	Project structure, tech stack
Output	.claude/commands/*.md files
Worker	ln-751-command-templates

Workflow

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

Generated Commands

Command	Purpose	Condition
refresh_context.md	Restore project context	Always
refresh_infrastructure.md	Restart services	Always
build-and-test.md	Full verification	Always
ui-testing.md	UI tests with Playwright	If Playwright detected
deploy.md	Deployment workflow	If CI/CD config exists
database-ops.md	Database operations	If database detected

Variables Extracted

Variable	Source	Example
`{{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

Variables reference: references/variables_reference.md
Questions: references/questions_commands.md

Version: 2.0.0 Last Updated: 2026-01-10

---name: ln-750-commands-generator-2description: Generates project-specific .claude/commands for Claude Code---> **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-bootstrapGenerates `.claude/commands/` with project-specific Claude Code commands.---## Overview| Aspect | Details ||--------|---------|| **Input** | Project structure, tech stack || **Output** | .claude/commands/*.md files || **Worker** | ln-751-command-templates |---## Workflow1. **Analyze** project structure and detect tech stack2. **Extract** variables (paths, ports, frameworks)3. **Delegate** to ln-751 with template name and variables4. **Verify** generated commands exist---## Generated Commands| Command | Purpose | Condition ||---------|---------|-----------|| refresh_context.md | Restore project context | Always || refresh_infrastructure.md | Restart services | Always || build-and-test.md | Full verification | Always || ui-testing.md | UI tests with Playwright | If Playwright detected || deploy.md | Deployment workflow | If CI/CD config exists || database-ops.md | Database operations | If database detected |---## Variables Extracted| Variable | Source | Example ||----------|--------|---------|| `{{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- **Variables reference:** [references/variables_reference.md](references/variables_reference.md)- **Questions:** [references/questions_commands.md](references/questions_commands.md)---**Version:** 2.0.0**Last Updated:** 2026-01-10

Frequently asked questions

Ln 750 Commands Generator