hm-init

Name: hm-init
Availability: InStock
Author: rodrigohighermind

Create a secure, architecture-first project scaffold with stack selection and quality gates.

184|43|Updated Mar 13, 2026

Search Tags:#devops #architecture #security #docker #best-practices #project-setup #init

Ready to run

npx skills add https://github.com/rodrigohighermind/highermind-code-skills --skill hm-init

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hm-init
Source: https://github.com/rodrigohighermind/highermind-code-skills/tree/main/hm-init
Command: npx skills add https://github.com/rodrigohighermind/highermind-code-skills --skill hm-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a proven blueprint to start a new software project with security and architecture-first decisions, translating the founder's vision into a robust, scalable repository from day one.

Core Features & Use Cases

Guided stack selection aligned with the project's needs, balancing security, performance, and maintainability.
Architecture-first setup that clearly defines module boundaries, naming conventions, and project structure.
Predefined quality gates, documentation templates, and CI readiness to accelerate safe delivery.
Foundations for security and reproducibility, including Docker/Dockerfile best practices and local infra considerations.
Documentation of key decisions to improve onboarding, risk awareness, and cost planning.

Quick Start

Describe your project goal and I will generate a secure, architecture-first project scaffold with architecture-first guidance.

Frequently Asked Questions about hm-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up a new software project with secure Docker practices from scratch?▼

Setting up a secure project from scratch requires defining module boundaries, enforcing Dockerfile security with non-root users and multi-stage builds, and establishing clear repository conventions from day one.

What is architecture-first project setup and why is it important for new repositories?▼

Architecture-first setup is an approach that defines module boundaries, naming conventions, and project structure before coding, ensuring scalable repositories that reduce onboarding risks and long-term costs.

How do I create a project scaffold that includes quality gates and CI readiness?▼

Creating a project scaffold with quality gates and CI readiness involves predefining documentation templates, selecting an aligned tech stack, and enforcing mandatory practices like multi-stage Docker builds during project kick-off.

Does this project initialization approach work for teams needing local infrastructure and security foundations?▼

Yes, this project initialization approach works for engineering teams by providing foundations for security and reproducibility, including Docker best practices and local infrastructure considerations tailored to the project's needs.

What's the best way to document architecture decisions during project kick-off?▼

The best way to document architecture decisions during kick-off is using predefined templates that capture stack selection rationale, security choices, and key architectural boundaries to improve onboarding and risk awareness.

When should I not use an automated project scaffold generator for my repository?▼

You should avoid automated project scaffold generators when your project requires highly specialized, non-standard architectural patterns that cannot accommodate predefined module boundaries, naming conventions, or mandatory Docker security practices.