- Home
- Skills
- Mjunaidca
- Mjs Agent Skills
- Blueprint Skill Creator
blueprint-skill-creator_skill
- Python
19
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill mjunaidca/mjs-agent-skills --skill blueprint-skill-creator- SKILL.md8.9 KB
Overview
This skill creates blueprint-driven skills for infrastructure and deployment tasks, bundling reusable templates with a mandatory impact analysis. It helps teams generate Dockerfiles, Helm charts, Kubernetes manifests, and CI/CD pipelines that are context-aware and production-ready. The outputs include parameterized templates, topology notes, and auth/CORS guidance to avoid common runtime failures.
How this skill works
The skill scans the target project to detect environment variables, build-time vs runtime usage, localhost references, and service dependencies. It runs a network topology and auth/CORS impact analysis to map localhost to service names and surface callback or origin changes needed for containers. Finally, it generates parameterized templates (Dockerfile, compose, charts, pipeline snippets) plus an impact checklist and gotchas documentation to guide safe deployment.
When to use it
- Creating a new deployment skill that must produce templates or reference configs (Dockerfile, Helm chart, manifest).
- Containerizing an existing app where environment, network, or auth behavior will change.
- Building CI/CD pipelines that must separate build-time and runtime secrets and steps.
- Designing multi-service topologies that require service name mapping and health/startup ordering.
- Auditing a produced template to ensure it won’t break in staging or production.
Best practices
- Always perform impact analysis before generating assets: environment, network topology, auth/CORS, and dependencies.
- Differentiate build-time ARGs from runtime ENVs and document which variables are secrets.
- Replace localhost references with service names appropriate for Docker or Kubernetes and include example URLs.
- Parameterize templates and document required variables, ports, and startup order.
- Include health checks, resource limits, and clear instructions for secrets management (external stores or K8s secrets).
Example use cases
- Generate a production-ready multi-stage Dockerfile for a Python web app with documented ENV and ARG usage.
- Produce a docker-compose template that maps service names, ports, and startup dependencies for local multi-service testing.
- Create a Helm chart skeleton with values.yaml patterns, secret handling guidance, and resource limit presets for staging and prod.
- Build a CI/CD pipeline blueprint that separates build artifacts, injects secrets securely, and runs integration health checks before deploy.
- Audit an existing template to find missing CORS origins, hardcoded localhost URLs, or baked-in secrets and produce remediation notes.
FAQ
It flags secrets found in files or env usage, recommends external secret stores or K8s secrets, and marks which variables must be replaced at deploy time.
Will generated templates work in both Docker Compose and Kubernetes?
Templates are parameterized and include notes for both Compose and Kubernetes; specific chart or compose assets are generated when that domain is requested.