Markdown Prompts

Send the entire response as ONE uninterrupted ```markdown fenced block only. No prose before or after. No nested code blocks. No formatting outside the block.

Generate a single-page, print-optimized cheat sheet + pocket reference card for Basecamp + the official Basecamp CLI (basecamp).

Design constraints (non-negotiable):
- One US Letter page (8.5×11"), portrait, 0.4" margins maximum.
- High-density but instantly scannable. Zero fluff. Every line earns its space.
- Visual hierarchy: bold section headers, monospace for every command, subtle visual separators.
- Two logical zones on the page:
  1. Left 60% → Core CLI reference (commands + patterns)
  2. Right 40% → Agent invariants, profiles, config, mental models, troubleshooting
- Bottom strip (full width) → One-line “Daily Agent Loop” and the single most important rule.
- Use pure Markdown + minimal CSS that prints cleanly (or generate a polished PDF/DOCX if the tool supports it). No decorative graphics that waste ink or space.
- Must be usable both as a desk reference (printed once, laminated preferred) and as a quick “always look at” card.

Content requirements (drawn from Basecamp CLI Mastery principles):

1. Installation & Auth (ultra-compact)
2. Profiles (multi-agent identities) — create / set-default / per-command usage
3. Project-local config (.basecamp/config.json) — exact recommended structure + how agents must use it
4. Agent Invariants (the 6 non-negotiable rules) — numbered, bold, impossible to miss
5. Output modes table: --json / --agent / --jq / --md / --ids-only + when to use each
6. Core command patterns (the real workhorses only):
   - Discovery & navigation
   - Todos (create, list, complete, assign, sweep, due dates)
   - Cards / Kanban (create, move, done)
   - Messages / Chat / Comments (including deterministic mentions)
   - Files & attachments
   - Reports, gauges, schedule
7. Breadcrumb chaining & --agent --help introspection habit
8. Mentions pattern: [@Name](mention:SGID) preferred form
9. Daily agent loop pattern (one tight example)
10. Troubleshooting one-liners (doctor, auth, noninteractive, config check)

Tone & style of the sheet itself:
- Extremely high signal. Ruthless prioritization.
- Commands shown with the most common useful flags already attached.
- Prefer real, copy-pasteable examples over abstract descriptions.
- Assume the reader is an AI agent or power user who will run these in a terminal.

Output format preference:
- First deliver a clean, print-ready Markdown version that can be pasted into a browser or Markdown-to-PDF tool.
- If the environment supports it, also produce a polished single-page PDF optimized for printing (high contrast, no color backgrounds that waste ink).

Finally, add a tiny footer line: “Basecamp CLI Mastery — Agent-First Reference | Follow the breadcrumbs.”

Make the sheet so good that someone would actually print it, laminate it, and keep it next to their keyboard forever.

# Technical Documentation taste of a developer-focused writer
- Keep docs in the same repository as the code and review them in the same pull request as the change. Confidence: 0.95
- Write in Markdown or MDX and build the site with a static generator such as Docusaurus, Starlight or MkDocs. Confidence: 0.85
- Organize content into tutorials, how-to guides, reference and explanation, following the Diataxis model. Confidence: 0.85
- Open the README with one sentence on what the project does, then install and a working quick start within the first screen. Confidence: 0.95
- Make every code sample copy-pasteable and runnable, with imports and realistic values included. Confidence: 0.95
- Test code samples in CI or extract them from tested example files so they never rot. Confidence: 0.80
- Generate API reference from the source, such as OpenAPI, TypeDoc or docstrings, instead of writing it by hand. Confidence: 0.90
- Write in second person and active voice with short sentences and plain words. Confidence: 0.90
- Use task-based headings like "Rotate an API key" rather than vague ones like "Keys". Confidence: 0.85
- State prerequisites and versions at the top of every guide. Confidence: 0.85
- Show the expected output after each command so readers know they are on track. Confidence: 0.80
- Lint prose with Vale and a shared style guide, and check links on every build. Confidence: 0.80
- Use admonitions such as Note and Warning sparingly, only for information that changes what the reader does. Confidence: 0.75
- Prefer diagrams as code with Mermaid so they can be reviewed and updated like text. Confidence: 0.75
- Keep a changelog in Keep a Changelog format and write migration guides for every breaking change. Confidence: 0.90
- Record architecture decisions as short ADRs that explain the context and the tradeoffs, not only the choice. Confidence: 0.85
- Give every page an owner and a last-reviewed date, and remove pages that are no longer true. Confidence: 0.75
- Add a search box and stable deep links to headings before adding any other site feature. Confidence: 0.80
- Write alt text for every screenshot and avoid screenshots of text that could be a code block. Confidence: 0.85
- Collect feedback with a simple "Was this page helpful?" widget and review the results monthly. Confidence: 0.65
- Document error messages by their exact text so users can find the fix by searching. Confidence: 0.85