# AI use cases for Agent Notion Template Docs (heyman333/agent-notion-template-docs) Repo: [heyman333/agent-notion-template-docs](https://github.com/heyman333/agent-notion-template-docs) | Use cases: 4 | Page: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/ notion-doc is an agent skill that gives AI-written HTML documents a Notion-like visual style using one fixed template and a linter. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Turn an agent-written report into a Notion-style HTML doc: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/notion-style-report-claude-code/ - Check an HTML document for style drift before sharing it: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/lint-html-docs-against-template/ - Write an incident postmortem with highlighted code and status callouts: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/incident-postmortem-with-code-blocks/ - Run the lint hook on every HTML write in Codex: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/codex-lint-hook-manual-setup/ ## How to turn an agent-written report into a Notion-style HTML doc with Agent Notion Template Docs Repo: [heyman333/agent-notion-template-docs](https://github.com/heyman333/agent-notion-template-docs) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Install the notion-doc plugin in Claude Code so requested reports come out in a Notion-like style. **Who it is for:** A team lead or analyst using Claude Code who asks the agent to write reports, summaries, or postmortems and wants them to look like Notion pages instead of a generic AI style. **The problem:** Agent-written documents often arrive with purple gradients, emoji-heavy headings, and drop-shadow cards that look nothing like the team's Notion pages. **The outcome:** Requested documents are written as HTML that follows the notion-doc template, with the agent supplying the content and outline while the skill handles presentation. ### Steps 1. Run `/plugin marketplace add heyman333/agent-notion-template-docs` in Claude Code. 2. Run `/plugin install notion-doc@agent-notion-template-docs`. 3. Restart Claude Code to apply the install. 4. Ask for a document, for example "Write this up as a report", or force the skill with `/notion-doc:notion-doc`. 5. Open the generated HTML file in a browser to check the layout. ### Prompt to paste into your agent ```text Using the notion-doc skill from heyman333/agent-notion-template-docs, write a report about from as a single HTML file named .html. Build it from skills/notion-doc/template.html with no new CSS and no inline styles. Verify that the file renders in a browser with the callouts, headings, and 720px content width intact. ``` ### Caveat The skill only controls presentation, so the agent still has to produce the content and outline, and the template must be kept intact for the output to match. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/notion-style-report-claude-code/ ## How to check an HTML document for style drift before sharing it with Agent Notion Template Docs Repo: [heyman333/agent-notion-template-docs](https://github.com/heyman333/agent-notion-template-docs) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Run lint.py on an HTML file to catch new CSS, inline styles, or invented classes. **Who it is for:** A writer or reviewer who has an HTML document, possibly edited by hand or by an agent, and needs to confirm it still follows the Notion-style template before it goes out. **The problem:** Hand edits and agent output can quietly add shadows, gradients, inline styles, or classes that are not in the template, breaking the consistent look. **The outcome:** A list of errors such as css-drift or unknown-class for the file, so the author can fix each one by picking from the template's block set. ### Steps 1. Clone the repo with `git clone https://github.com/heyman333/agent-notion-template-docs` and change into the folder. (inferred, check the README) 2. Run `python3 skills/notion-doc/lint.py mydoc.html` with the path to your document. 3. Read each ERROR line, which names the rule such as css-drift or unknown-class. 4. Replace new CSS, inline styles, or invented classes with blocks from the template. 5. Run the same lint command again until the file reports no errors. ### Prompt to paste into your agent ```text In the cloned heyman333/agent-notion-template-docs repo, run `python3 skills/notion-doc/lint.py .html` and fix every ERROR it reports by using only classes and CSS from skills/notion-doc/template.html. Save the corrected file in place. Verify that the final lint run prints no ERROR lines for that file. ``` ### Caveat The linter checks against template.html only, so a document can pass lint and still need a human review for content and tone. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/lint-html-docs-against-template/ ## How to write an incident postmortem with highlighted code and status callouts with Agent Notion Template Docs Repo: [heyman333/agent-notion-template-docs](https://github.com/heyman333/agent-notion-template-docs) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Produce an incident analysis with syntax-highlighted code and red or yellow callouts for severity. **Who it is for:** An engineer or on-call lead who has to write up an incident and wants the technical details, code snippets, and severity notes laid out clearly for the team. **The problem:** Postmortems mix logs, code, and warnings, and plain agent output makes the code and risk levels hard to scan. **The outcome:** An HTML postmortem with Prism-highlighted code blocks, a red warning callout, and a yellow caution callout that follows the Notion-style template. ### Steps 1. Install the skill in Claude Code or Codex using the plugin steps or by copying the `skills/notion-doc` folder. 2. Ask the agent to write a postmortem and to include the relevant code or log snippets. 3. Check that each code block has a `language-*` class so it is highlighted. 4. Run `python3 skills/notion-doc/lint.py .html` on the output. (inferred, check the README) 5. Open the file in a browser and confirm the red and yellow callouts show the right severity. ### Prompt to paste into your agent ```text Using the notion-doc skill from heyman333/agent-notion-template-docs, write a postmortem for using the notes in into .html. Include code blocks with language classes, a red warning callout, and a yellow caution callout. Verify that lint.py reports no errors for the output file. ``` ### Caveat The sample incident analysis in examples is in Korean, and the README does not describe a tested English postmortem workflow beyond the English campaign sample. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/incident-postmortem-with-code-blocks/ ## How to run the lint hook on every HTML write in Codex with Agent Notion Template Docs Repo: [heyman333/agent-notion-template-docs](https://github.com/heyman333/agent-notion-template-docs) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Wire the PostToolUse lint hook into Codex so each written HTML document is checked automatically. **Who it is for:** A developer who installs the skill by hand in Codex instead of as a plugin and wants every agent-written HTML file checked without a manual lint step. **The problem:** A manual install does not include the lint hook, so agent-written documents can drift from the template without any warning. **The outcome:** Each HTML file the agent writes or edits triggers the hook, which reports what needs fixing or reminds the agent to use the skill. ### Steps 1. Copy the skill with `mkdir -p ~/.agents/skills && cp -r skills/notion-doc ~/.agents/skills/` for all projects. 2. Open `~/.codex/hooks.json`, or create it if it does not exist. 3. Add a PostToolUse entry with matcher `Write|Edit|apply_patch` that runs `/path/to/agent-notion-template-docs/hooks/notion-doc-lint.py`. 4. Start a new Codex session so the skill and hook are picked up. 5. Ask for a document and confirm the hook reports any problems in the written HTML. ### Prompt to paste into your agent ```text Configure Codex on this machine to run the notion-doc lint hook from the heyman333/agent-notion-template-docs repo as a PostToolUse command for Write, Edit, and apply_patch in ~/.codex/hooks.json. Keep any existing hook entries. Verify by writing a test HTML file and confirming the hook prints a lint result. ``` ### Caveat The README says a manual install does not bring the hook along, so this JSON edit must be done by hand and the hook only covers document files, not apps or build output. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/heyman333-agent-notion-template-docs/codex-lint-hook-manual-setup/