nathan
016d38d5ab
- Add service management prompts (review, standardize, troubleshoot, integration) - Add Docker Swarm migration and tutoring workflows (swarm-migration, swarm-tutor) - Add SSO onboarding guide for Authentik integration (sso-onboarding) - Add session lifecycle prompts (start, end, status) for context continuity - Add node bootstrap scripts for Debian Trixie (day0bootstrap.sh) and Ubuntu/Debian (pi_init.sh) These prompts implement gated, step-by-step workflows with explicit confirmation requirements to prevent accidental changes during service operations. Bootstrap scripts standardize IP configuration (10.0.0.200) and install Docker + Ansible on new nodes.
20 lines
1.6 KiB
Markdown
20 lines
1.6 KiB
Markdown
"I am finalizing my Homelab & Automation repository. This is my personal 'digital workshop' where I build things for fun, experimentation, and to master my craft. You are acting as a Senior Systems Architect giving a peer-review of my workshop layout.
|
||
|
||
The Objective: Evaluate the repository for Engineering Craft. Does this look like a well-organized lab where a curious engineer is mastering Docker, Ansible, and SQL?
|
||
|
||
Your Task (Gated Workflow):
|
||
|
||
|
||
Gate 1: The 'Shop Layout' (Structure & Discovery) – Look at my top-level folders (ansible, compose, scripts, etc.). Is the taxonomy intuitive for a fellow hobbyist? Check the top-level README. Does it share the 'Joy of the Lab' and explain my hardware/hypervisor choices?
|
||
|
||
Gate 2: Jargon Scrub & Tone Check – Identify any 'Corporate Jargon' that feels out of place in a personal lab (e.g., 'Contracts', 'Personas', 'SOPs'). Provide a list of suggested renames to make the documentation sound more like a Technical Specification for a personal project.
|
||
|
||
Gate 3: Automation Logic & 'Cyborg' Pairing – Review my Networking.md or any Ansible files. Does my documentation explain how I 'pair' with AI (Microsoft Copilot) to navigate complex configs like the non-standard AR SQL or tricky date-literal parsing?
|
||
|
||
Workflow Constraints:
|
||
|
||
Atomic Edits: Provide specific improvements for one folder or README at a time.
|
||
|
||
Tone: Peer-level, candid, and engineering-focused.
|
||
|
||
The First Gate: Acknowledge the 'Workshop' focus and start with Gate 1. Based on my folder list and README, is this an organized engineering lab or a 'junk drawer' of scripts?" |