Operating Linux as a Primary OS Suite

You are a Linux workstation architect for power users.

Context:
- My hardware: {{hardware}} (CPU/GPU/RAM, laptop/desktop)
- My role/use cases: {{use_cases}} (default: “engineering work: dev, automation, cloud admin, documentation, Teams/Meetings”)
- Security requirements: {{security_level}} (default: “workstation with full disk encryption, strong updates, least privilege”)
- Preferred distro family: {{distro_preference}} (default: “Ubuntu/Debian or Fedora”)
- Must-have apps: {{must_have_apps}} (e.g., VS Code, Git, Docker/Podman, browser profiles, password manager)
- Constraints: {{constraints}} (e.g., “needs to work in corporate environment, VPN, SSO, smartcard/YubiKey if applicable”)

Task:
Create a complete “Linux as primary OS” operating suite plan that I can follow end-to-end.

Requirements:
1) Recommend 2 distro options (primary + alternative) and justify based on stability, security, and productivity.
2) Provide a setup checklist in order:
   - Installation choices (partitioning guidance, filesystem, full disk encryption)
   - Firmware/BIOS considerations (Secure Boot stance + rationale)
   - User management (sudo strategy, separate admin account guidance)
   - Updates/patching model (automatic vs manual, rollback options)
   - Backup strategy (local + remote, frequency, restore test)
3) Provide a “daily driver productivity stack”:
   - Terminal + shell + prompt
   - Dev stack (Node, Python, containers)
   - Office/Collaboration (browser profiles, Teams alternatives if needed, calendar)
   - Notes + docs workflow (Markdown, PDF, diagram tools)
4) Provide a hardening baseline:
   - Firewall, disk encryption verification, SSH stance, audit logging basics
   - Secrets management (how to store API keys safely)
   - Browser security and phishing resistance
5) Provide a troubleshooting playbook:
   - Wi-Fi/VPN issues
   - Display/HiDPI
   - Audio/bluetooth
   - Printer/scanner
   - Docker/Podman networking
6) Include a “done definition” checklist and a 30-day maintenance routine.

Output format:
- “Recommended Setup” (with reasoning)
- “Step-by-step Implementation Checklist”
- “App/Tooling Stack”
- “Security Baseline”
- “Troubleshooting”
- “Maintenance & Done Definition”

Keep it pragmatic: commands where helpful, but explain why each step matters.

You are a Linux workstation architect for power users.

Context:
- My hardware: {{hardware}} (CPU/GPU/RAM, laptop/desktop)
- My role/use cases: {{use_cases}} (default: “engineering work: dev, automation, cloud admin, documentation, Teams/Meetings”)
- Security requirements: {{security_level}} (default: “workstation with full disk encryption, strong updates, least privilege”)
- Preferred distro family: {{distro_preference}} (default: “Ubuntu/Debian or Fedora”)
- Must-have apps: {{must_have_apps}} (e.g., VS Code, Git, Docker/Podman, browser profiles, password manager)
- Constraints: {{constraints}} (e.g., “needs to work in corporate environment, VPN, SSO, smartcard/YubiKey if applicable”)

Task:
Create a complete “Linux as primary OS” operating suite plan that I can follow end-to-end.

Requirements:
1) Recommend 2 distro options (primary + alternative) and justify based on stability, security, and productivity.
2) Provide a setup checklist in order:
   - Installation choices (partitioning guidance, filesystem, full disk encryption)
   - Firmware/BIOS considerations (Secure Boot stance + rationale)
   - User management (sudo strategy, separate admin account guidance)
   - Updates/patching model (automatic vs manual, rollback options)
   - Backup strategy (local + remote, frequency, restore test)
3) Provide a “daily driver productivity stack”:
   - Terminal + shell + prompt
   - Dev stack (Node, Python, containers)
   - Office/Collaboration (browser profiles, Teams alternatives if needed, calendar)
   - Notes + docs workflow (Markdown, PDF, diagram tools)
4) Provide a hardening baseline:
   - Firewall, disk encryption verification, SSH stance, audit logging basics
   - Secrets management (how to store API keys safely)
   - Browser security and phishing resistance
5) Provide a troubleshooting playbook:
   - Wi-Fi/VPN issues
   - Display/HiDPI
   - Audio/bluetooth
   - Printer/scanner
   - Docker/Podman networking
6) Include a “done definition” checklist and a 30-day maintenance routine.

Output format:
- “Recommended Setup” (with reasoning)
- “Step-by-step Implementation Checklist”
- “App/Tooling Stack”
- “Security Baseline”
- “Troubleshooting”
- “Maintenance & Done Definition”

Keep it pragmatic: commands where helpful, but explain why each step matters.