- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
Designer role. Reads outline, generates a single HTML presentation file with CSS design system + JS slide engine + per-slide content. Accepts visual references (URLs, screenshots, design specs) and extracts design signals to inform the isomorphic mapping. Use whenever the user says "design slides", "generate deck", "generate the deck", "build slides", "visual style", "reference this style", "like this design", "design", "generate slides", "visual style", "reference this style", or wants to turn an outline into actual slides. --- # codeck design ## Role activation Read `$DECK_DIR/diagnosis.md` for the recommended design role and its structural mapping. You are that person. Their formal logic — how they organize space, tension, rhythm — becomes your visual logic. The role is chosen for structural match, not domain: > Content builds layer by layer, each page adding complexity → Ravel (Bolero): visual simplicity to richness, color gradually saturates, each page adds one element. > > Content driven by contrast and opposing forces → Caravaggio: high-contrast lighting, black-white dominant, accent color used sparingly like a decisive stroke. > > Content strips away noise to reveal one truth → Dieter Rams: remove everything unnecessary, final slide is the emptiest and most powerful. Apply their formal logic directly. Don't explain their principles — embody them in every visual choice. If `diagnosis.md` doesn't exist, use AskUserQuestion or recommend running `/codeck` first. ## AskUserQuestion format 1. **Re-ground** — "codeck design, {current step}" 2. **Simplify** — plain language 3. **Recommend** — suggestion + reason 4. **Options** — choices Only state verified facts. For unrendered results, say "will" not "is". ## Setup ```bash DECK_DIR="$HOME/.codeck/projects/$(basename "$(pwd)")" mkdir -p "$DECK_DIR" bash "$HOME/.claude/skills/codeck/scripts/status.sh" "$DECK_DIR" ``` Read `$DECK_DIR/outline.md` — page structure, content points, user intent, note to designer. Read `$D
Scaffold and guide creation of a new pubm plugin package
Control the user's real browser via Real Browser MCP. Use when asked to interact with web pages, test UIs, fill forms, or read page content.
Use when starting or continuing a full CQA 2.1 content quality assessment. Guides through all three tabs (Pre-migration, Quality, Onboarding) parameter by parameter.
Add a new external skill to the agent-skills project. Scaffolds the skill directory, registers it in the publish workflow, and creates the Claude Code symlink. Use when adding any new skill to skills/.
- 📁 .claude-plugin/
- 📁 .codex-plugin/
- 📁 docs/
- 📄 .gitignore
- 📄 AGENTS.md
- 📄 CLAUDE.md
Use when a well-specified task has meaningful design choices and you want to maximize quality by comparing multiple independent attempts. Works for coding, writing, and custom task types. Triggers on "slot-machine", "best-of-N", "pull the lever", "parallel implementations", or when quality matters more than speed and the spec is clear enough for independent work.
- 📁 references/
- 📁 templates/
- 📄 SKILL.md
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Converts documents and knowledge gathered from Microsoft Copilot into well-structured, SharePoint-compatible markdown files. Use when a user has content from Copilot (summaries, research, meeting notes, process steps) and wants to produce a formatted page for a SharePoint site, wiki, or knowledge base. Triggers include "create a markdown file from this", "format this for SharePoint", "write this up as a knowledge base article", "turn this Copilot output into a page", or when a user pastes Copilot-generated content and asks for it to be documented.
- 📄 requirements.txt
- 📄 SKILL.md
Control a real, local web browser to search, navigate, and extract information.
This skill should be used when the user asks to "add accessibility", "check ARIA", "handle keyboard navigation", "add focus management", or creates UI components, forms, or interactive elements. Provides WCAG 2.2 AA patterns for keyboard navigation, ARIA roles and states, focus management, color contrast, and screen reader support.
- 📁 assets/
- 📁 commands/
- 📁 docs/
- 📄 .gitignore
- 📄 .skillshare-meta.json
- 📄 audit-permissions
A strategic thinking partner for Claude Code that separates deciding from building. Challenges assumptions, compares approaches, and hands execution a ready-to-run prompt in a fresh session. Handles skill routing, context handoff, and memory management.
Use when looking up library documentation, API references, framework patterns, or code examples for ANY library (React, Next.js, Vue, Django, Laravel, etc.). Fetches current docs via Context7 REST API. Triggers on: how to use library, API docs, framework pattern, import usage, library example.
