Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,14 @@
"version": "0.1.0",
"keywords": ["video", "transcript", "screenshots", "yt-dlp", "reference-material"],
"category": "utilities"
},
{
"name": "zae",
"source": "./plugins/zae",
"description": "Hand-picked skills, agents, commands and output styles from other plugins, pinned to an upstream commit, plus our own",
"version": "0.1.0",
"keywords": ["curated", "skills", "writing", "vendored"],
"category": "productivity"
}
]
}
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,14 @@ A collection of Claude Code plugins for ZeroAE development standards and workflo
|--------|-------------|
| [`zstd`](plugins/zstd/) | Organization-wide development standards and conventions |
| [`cspy`](plugins/cspy/) | Architecture patterns from [Cosmic Python](https://cosmicpython.com) for domain-driven design |
| [`dynamodb`](plugins/dynamodb/) | DynamoDB single-table design patterns, schema design and audits, based on Rick Houlihan's re:Invent talks |
| [`vidref`](plugins/vidref/) | Extract transcripts and screenshots from videos for skill reference material |
| [`zae`](plugins/zae/) | Hand-picked skills from other plugins, pinned to an upstream commit, plus our own |

## Installation

```
/plugin marketplace add zeroae/claude-plugins
/plugin install {plugin-name}@zeroae.com
```

Expand Down
2 changes: 1 addition & 1 deletion plugins/cspy/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"author": {
"name": "ZeroAE"
},
"repository": "https://github.com/zeroae/.claude",
"repository": "https://github.com/zeroae/claude-plugins",
"license": "CC-BY-NC-ND-3.0",
"keywords": ["architecture", "ddd", "patterns", "python", "cosmic-python", "repository-pattern", "unit-of-work", "cqrs", "event-driven"],
"skills": "./skills/"
Expand Down
2 changes: 1 addition & 1 deletion plugins/dynamodb/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"name": "ZeroAE",
"url": "https://github.com/zeroae"
},
"repository": "https://github.com/zeroae/.claude",
"repository": "https://github.com/zeroae/claude-plugins",
"license": "MIT",
"keywords": ["dynamodb", "nosql", "aws", "data-modeling", "single-table-design"],
"skills": "./skills/"
Expand Down
7 changes: 3 additions & 4 deletions plugins/dynamodb/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,13 @@ Expert guidance on DynamoDB schema design using NoSQL-native patterns:
|-------|---------------|
| `help` | "How do I use the DynamoDB plugin?", `/dynamodb:help` |
| `patterns` | Asking about DynamoDB design, access patterns, single-table design, GSIs |
| `design` | "Help me design a DynamoDB schema for X", "Model my data for DynamoDB" |
| `audit` | "Audit my DynamoDB schema", "Review this table design", "Check for issues" |
| `schema` | Design a new schema ("Help me design a DynamoDB schema for X", "Model my data for DynamoDB") or audit an existing one ("Audit my DynamoDB schema", "Review this table design") |

## Agents

| Agent | Triggers When |
|-------|---------------|
| `schema-auditor` | User shares DynamoDB code (CDK/CloudFormation/Terraform) and asks for feedback |
| `auditor` | User shares DynamoDB code (CDK/CloudFormation/Terraform) and asks for feedback |

## Usage Examples

Expand Down Expand Up @@ -54,7 +53,7 @@ Expert guidance on DynamoDB schema design using NoSQL-native patterns:

## Diagram Outputs

The `design` skill generates visual diagrams to help understand schema structure:
The `schema` skill generates visual diagrams to help understand schema structure:

| Diagram Type | Format | Purpose |
|--------------|--------|---------|
Expand Down
2 changes: 1 addition & 1 deletion plugins/vidref/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"name": "ZeroAE",
"url": "https://github.com/zeroae"
},
"repository": "https://github.com/zeroae/.claude",
"repository": "https://github.com/zeroae/claude-plugins",
"license": "MIT",
"keywords": ["video", "transcript", "screenshots", "yt-dlp", "reference-material"],
"skills": "./skills/"
Expand Down
13 changes: 13 additions & 0 deletions plugins/zae/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
{
"name": "zae",
"version": "0.1.0",
"description": "Hand-picked skills, agents, commands and output styles from other plugins, pinned to an upstream commit, plus our own",
"author": {
"name": "ZeroAE",
"url": "https://github.com/zeroae"
},
"repository": "https://github.com/zeroae/claude-plugins",
"license": "MIT",
"keywords": ["curated", "skills", "writing", "vendored"],
"skills": "./skills/"
}
79 changes: 79 additions & 0 deletions plugins/zae/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# zae

Hand-picked pieces of other people's plugins, one skill (or agent, command,
output style) at a time, next to ones we write ourselves. Call them as
`/zae:<name>`.

## Install

```
/plugin marketplace add zeroae/claude-plugins
/plugin install zae@zeroae.com
```

On Claude Code 2.1.275 or later, one step does both:

```
/plugin install zae --marketplace zeroae/claude-plugins
```

## Skills

| Skill | Description | From |
|-------|-------------|------|
| `unslop` | Cut AI tells from any writing | [pstack-claude](https://github.com/michael-denyer/pstack-claude/tree/main/plugins/pstack/skills/unslop) (poteto's pstack), MIT |

## Output styles

| Style | Description | From |
|-------|-------------|------|
| `zae-plain` | Plain, direct replies with no AI tells. Keeps Claude Code's coding instructions | Our own, condensed from `unslop`'s rules |

An output style applies to every reply in a session, so it is opt-in: pick it
with `/output-style`, or set `outputStyle` in `~/.claude/settings.json`. It
does not set `force-for-plugin`, so enabling `zae` does not turn it on.

## Picked vs. our own

A picked component is a copy of an upstream file or folder at a pinned
commit. [`vendored.json`](vendored.json) records, for each one, the upstream
repo and path, the commit, the git object id, the license and a hash of the
copied files. Do not edit a picked component by hand: `check` fails on it.
To change one, make it our own (below).

Anything under `skills/`, `agents/`, `commands/` or `output-styles/` that
`vendored.json` does not list is our own. Write it here like in any other
plugin.

## Managing picks

From the repo root:

```bash
# Pick a skill: a GitHub tree URL gives repo, ref and path in one go
scripts/zae-vendor.py add https://github.com/<owner>/<repo>/tree/main/skills/<name>

# Or owner/repo and a path; --as renames it or says what kind it is
scripts/zae-vendor.py add <owner>/<repo> plugins/x/agents/reviewer.md --as agents/reviewer.md

scripts/zae-vendor.py status # which picks are behind upstream HEAD (exit 2 = some are)
scripts/zae-vendor.py update skills/unslop # re-copy at upstream HEAD (or --ref <commit>)
scripts/zae-vendor.py update --all
scripts/zae-vendor.py check # copies match vendored.json
scripts/zae-vendor.py remove skills/unslop
```

`add` and `update` refuse upstreams with no LICENSE near the component, and
symlinks. They copy that license to `licenses/`. They print a REVIEW block
when what the component can run or widen changes: frontmatter `hooks`,
`allowed-tools`, `tools`, `mcpServers`, `permissionMode` or `model`, and
executable files. Read the diff before you commit, like any third-party code.

To make a picked component our own, so you can edit it: copy it aside,
`remove` it, put the copy back and edit away. Keep its license file in
`licenses/` and say where it came from in the table above.

## License

Our own content: MIT. Each picked component keeps its upstream license, copied
to [`licenses/`](licenses/) and named in `vendored.json`.
22 changes: 22 additions & 0 deletions plugins/zae/licenses/michael-denyer__pstack-claude.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
MIT License

Copyright (c) 2026 Lauren Tan
Copyright (c) 2026 Michael Denyer

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
47 changes: 47 additions & 0 deletions plugins/zae/output-styles/zae-plain.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
name: zae-plain
description: Plain, direct replies with no AI tells. Condensed from the unslop skill's rules.
keep-coding-instructions: true
---

# Plain replies

Write like an engineer talking to a colleague. These rules apply to your replies in chat. For an editing pass over a document, a README or a PR body, use the `unslop` skill, which has the full rules.

## Open and close

- Start with the answer. No "Great question!", "You're absolutely right!", "Of course!" or "Certainly!".
- End when the content ends. No "I hope this helps!", "Let me know if...", or a summary line that repeats what you just said.
- No closing lines about the future ("The future looks bright"). Give the next concrete step, or nothing.

## Words

- Use the plain word: "use", not "utilize" or "leverage". "Help", not "facilitate". "Many", not "numerous". "If", not "in the event that".
- Avoid stock AI vocabulary: additionally, crucial, delve, enhance, fostering, garner, interplay, intricate, landscape, pivotal, showcase, tapestry, testament, underscore, vibrant.
- Say "is" or "has". Not "serves as", "stands as", "boasts" or "features".
- Skip metaphor jargon when a concrete word exists: substrate, wedge, vector, nexus, paradigm, north star, flywheel, surface (as in "API surface"), primitive (as a noun), harness (as a metaphor).
- Name things once and keep the name. Don't cycle synonyms.

## Sentences

- One idea per sentence. Split a sentence that makes the reader backtrack.
- Prefer active voice and name the actor: "the loader parses the file", not "the file is parsed".
- Cut filler: "to", not "in order to". "Because", not "due to the fact that". Drop "It is important to note that".
- Hedge once, where the doubt is real: "may", not "could potentially possibly".
- No "not just X, but Y". State the point.
- Group things in the number they come in, not in threes by habit.
- Say what something does, with a mechanism or a number, not how it feels.
- Name the source of a claim, or drop the claim. No "experts say".

## Punctuation and formatting

- No em dashes. Use a period or a comma.
- Colons go before a list or an example, not between two halves of a sentence.
- Bold sparingly, for the one thing the reader must not miss.
- Headings in sentence case. Straight quotes.
- No decorative emojis in headings, bullets or prose.

## Exceptions

- Follow the project's conventions where they conflict with these rules. Gitmoji prefixes on ZeroAE commits and issue titles (`✨ feat(scope): ...`) are required, not decorative.
- Leave code, commands, file paths, URLs, quoted text and error messages exactly as they are.
61 changes: 61 additions & 0 deletions plugins/zae/skills/unslop/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
---
name: unslop
description: Cut AI tells from any writing.
---

# Unslop

Edit text to remove AI patterns. Scan for the patterns below, then rewrite. Preserve meaning and match the intended tone.

## Patterns to detect and fix

Rule numbers are stable ids that other skills cite. A removed rule leaves a gap.

### Content

3. **Superficial -ing phrases.** "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.
5. **Vague attributions.** "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.

### Language

7. **AI vocabulary.** Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore, vibrant. Replace with plain words.
8. **Fancy ways to say "is".** "serves as", "stands as", "boasts", "features". Say "is" or "has".
9. **"Not just X, but Y."** State the point directly instead.
10. **Rule of three.** Don't force ideas into groups of three. Use the natural number.
11. **Synonym cycling.** Protagonist, main character, central figure, hero all in one paragraph. Pick one, repeat it.
12. **False ranges.** "from X to Y" where X and Y aren't on a meaningful scale. List topics directly.

### Style

13. **Em dash overuse.** Avoid em dashes entirely. Use periods or commas only (no parentheses, no en dashes, no hyphen-as-dash substitutes). If a thought needs separation, end the sentence or use a comma.
14. **Colon overuse.** Colons are fine before a list or example, not as mid-sentence connectors. "If you're coming from traditional automation: instead of registering event handlers, you describe conditions" adds nothing with the colon. Rewrite to let the point stand on its own without comparison framing. "Describing when the scheduler should fire works best as plain English." Same meaning, no crutch punctuation.
15. **Boldface overuse.** Don't bold every proper noun or acronym.
16. **Inline-header lists.** The tell is a bold label and colon that restates the line: "**Performance:** Performance improved...". Convert those to prose. A bold lead-in that ends in a period, names the item, and is followed by genuinely new detail ("**Schema in TypeScript.** Tables live in one file.") is fine, not a tell.
17. **Title case headings.** Use sentence case.
18. **Decorative emojis.** Remove from headings and bullets.
19. **Curly quotes.** Use straight quotes.

### Communication artifacts

20. **Chatbot phrases.** "I hope this helps!", "Let me know if...", "Of course!", "Certainly!", "Found the smoking gun!" Remove.
22. **Sycophantic tone.** "Great question! You're absolutely right!" Respond directly.

### Filler

23. **Filler phrases.** "In order to" becomes "To". "Due to the fact that" becomes "Because". Delete "It is important to note that".
24. **Excessive hedging.** "could potentially possibly be argued that it might" becomes "may".
25. **Generic conclusions.** "The future looks bright." State specific plans or facts.

### Jargon

26. **Abstract metaphor nouns.** Substrate (base), wedge, wedge in (add), vector (way, method), locus, vantage, nexus, primitive as a noun, harness as a metaphor, surface as in "API surface", bedrock, scaffolding as a metaphor, modality, paradigm, gold-plating (more than the job needs), ratchet as a metaphor (the mechanism's real name, or a limit that only tightens), evacuate for moving code (move out), endgame (the last phase), north star, flywheel. These read as technical but usually have a plainer concrete word. Pick the concrete word.

### Plain speech

27. **Say what it does, not how it feels.** "the database stays close at hand", "SQL you can read", "types that follow your schema" name a feeling. The fix names the mechanism or a number: "`.toSQL()` returns the exact string sent to the database", "a column rename fails the build". Ask what the sentence tells the reader to do or know, then write that. If you can't restate it as a concrete instruction, fact, or number, cut it. One more check: if the sentence could appear unchanged in another project's docs, it says nothing about this one. Cut it.
28. **Shorten or split dense sentences.** If the reader has to backtrack to parse a sentence, break it in two or drop clauses. One idea per sentence.
29. **Active voice.** Prefer it. Catch "is/are/was/were + past participle" and name the actor: "queries are validated" becomes "the compiler validates queries", "the file is parsed by the loader" becomes "the loader parses the file". Passive is fine only when the actor is unknown or genuinely doesn't matter.
30. **Cut adverbs, or use a stronger verb.** "runs quickly" becomes "is fast" or the number, and "significantly improves" becomes the measured delta. An adverb propping up a weak verb means the verb is wrong.
31. **Prefer the plain word.** "utilize" and "leverage" become "use", "facilitate" becomes "help", "numerous" becomes "many", "in the event that" becomes "if". The fancier synonym is rarely clearer.
32. **Mannered prose.** Metaphor or flourish where a literal phrase exists: aphorisms ("wire it or delete it"), rhetorical fragments for effect, personified code ("the plan holds it"), figurative verbs ("rides along", "stands on"), stock framing phrases. "A dial worth turning" becomes "a parameter worth varying". Say what you mean. Rule 26 covers the metaphor nouns.
33. **Over-compression.** Dropped articles, verbless fragments, symbol-speak, and abbreviations that make the reader decode instead of read. "Parser rejects bad date → exit 2, no write" becomes "The parser rejects a bad date, exits with code 2, and writes nothing." Write whole sentences with their articles and verbs, and spell out arrows and abbreviations.
15 changes: 15 additions & 0 deletions plugins/zae/vendored.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
{
"components": {
"skills/unslop": {
"upstream": "https://github.com/michael-denyer/pstack-claude.git",
"path": "plugins/pstack/skills/unslop",
"ref": "d88063f3355a5ecff0e6dbb890a11bab4b08bc2e",
"object": "0c1e9c3014f788044725640bb0159562b5543068",
"license": "MIT",
"license_file": "licenses/michael-denyer__pstack-claude.txt",
"vendored_on": "2026-11-05",
"content_sha256": "acbe5327bed34310a121e825e5959c09c3ac63436ab873a252fff3d45c4b2bc6",
"needs_review": []
}
}
}
2 changes: 1 addition & 1 deletion plugins/zstd/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"author": {
"name": "ZeroAE"
},
"repository": "https://github.com/zeroae/.claude",
"repository": "https://github.com/zeroae/claude-plugins",
"license": "MIT",
"keywords": ["conventions", "standards", "commits", "github", "changelog"],
"skills": "./skills/"
Expand Down
Loading
Loading