From configure-plugin
Runs comprehensive infrastructure standards compliance checks and auto-configures fixes for frontend, infrastructure, or Python projects. Ideal for audits, new setups, CI/CD validation with --check-only or --fix.
npx claudepluginhub laurigates/claude-plugins --plugin configure-pluginThis skill is limited to using the following tools:
Run all infrastructure standards compliance checks.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Run all infrastructure standards compliance checks.
| Use this skill when... | Use another approach when... |
|---|---|
| Performing comprehensive infrastructure audit | Checking single component (use specific /configure:X skill) |
| Setting up new project with all standards | Project already has all standards configured |
| CI/CD compliance validation | Need detailed status only (use /configure:status) |
| Running initial configuration | Interactive component selection needed (use /configure:select) |
Batch-fixing all compliance issues with --fix | Manual review of each component preferred |
find . -maxdepth 1 -name \'.project-standards.yaml\'find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name '*.tf' \)find . -maxdepth 1 -type d \( -name 'terraform' -o -name 'helm' -o -name 'argocd' \)grep -m1 "^standards_version:" .project-standards.yamlParse from command arguments:
--check-only: Report status without offering fixes (CI/CD mode)--fix: Apply all fixes automatically without prompting--type <type>: Override auto-detected project type (frontend, infrastructure, python)Execute this comprehensive infrastructure standards compliance check:
.project-standards.yaml if it existsterraform/, helm/, argocd/, or *.tf filespackage.json with vue/react dependenciespyproject.toml or requirements.txt--type override if providedExecute each configure command in check-only mode using the SlashCommand tool:
/configure:makefile --check-only
/configure:pre-commit --check-only
/configure:release-please --check-only
/configure:dockerfile --check-only
/configure:container --check-only
/configure:skaffold --check-only
/configure:workflows --check-only
/configure:sentry --check-only
/configure:docs --check-only
/configure:github-pages --check-only
/configure:cache-busting --check-only
/configure:tests --check-only
/configure:coverage --check-only
/configure:memory-profiling --check-only
/configure:linting --check-only
/configure:formatting --check-only
/configure:dead-code --check-only
/configure:editor --check-only
/configure:security --check-only
Skip components that do not apply to the detected project type. For component applicability by project type, see REFERENCE.md.
Collect results from each check.
Print a summary table with each component's status (PASS/WARN/FAIL), overall counts, and a list of issues to fix. For report format template, see REFERENCE.md.
If --fix flag is set or user confirms:
--fixCreate or update .project-standards.yaml with the current standards version, project type, timestamp, and component versions. For template, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check (all components) | /configure:all --check-only |
| Auto-fix all issues | /configure:all --fix |
| Check standards file validity | test -f .project-standards.yaml && cat .project-standards.yaml | head -10 |
| List project type indicators | find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \) -exec basename {} \; |
| Count missing components | grep -c "status: missing" compliance-report.txt 2>/dev/null |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically |
--type <type> | Override project type (frontend, infrastructure, python) |
| Code | Meaning |
|---|---|
| 0 | All checks passed |
| 1 | Warnings found (non-blocking) |
| 2 | Failures found (blocking) |
For faster compliance checks on large projects, spawn teammates for parallel configuration checks:
| Teammate | Focus | Checks |
|---|---|---|
| Linting teammate | Code quality configs | linting, formatting, dead-code, editor |
| Security teammate | Security configs | security, pre-commit, container |
| Testing teammate | Test infrastructure | tests, coverage, memory-profiling |
| CI teammate | Deployment configs | workflows, release-please, dockerfile, skaffold |
This is optional -- the skill works sequentially without agent teams.
/configure:select - Interactively select which components to configure/configure:status - Quick read-only status overview/configure:pre-commit - Pre-commit specific checks/configure:release-please - Release automation checks/configure:dockerfile - Dockerfile configuration checks/configure:container - Comprehensive container infrastructure/configure:skaffold - Kubernetes development checks/configure:workflows - GitHub Actions checks/configure:sentry - Sentry error tracking checks/configure:docs - Documentation standards and generators/configure:github-pages - GitHub Pages deployment/configure:cache-busting - Cache-busting strategies/configure:tests - Testing framework setup/configure:coverage - Code coverage configuration/configure:memory-profiling - Memory profiling with pytest-memray/configure:linting - Linter configuration/configure:formatting - Code formatter setup/configure:dead-code - Dead code detection/configure:editor - Editor/IDE configuration/configure:security - Security scanning