Results for “zettelkasten”

Use the note-management skill to capture a new fleeting note titled

Creates pastel-toned, lifestyle-oriented presentation decks with rounded cards, soft glow blobs, and Playfair italic numbering.

Ingests case studies, past proposals, and boilerplate from library/inbox into structured indexes. Use when the user requests to 'index proposal library', 're-index case studies', 'ingest inbox docs', or 'validate library'.

Text Claude from your phone — set up the njerschow/textme daemon so inbound iMessages drive a Claude Code session on your laptop, with voice notes, image input, code execution, and a phone-number whitelist.

Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

Explore codebases efficiently using AST-based structural search, outline, and symbol unfolding to reduce token usage.

Create bucket lists with categorization and planning. TRIGGERS - Use when user needs help with bucket-list related tasks.

Creates hand-drawn wireframes with graph-paper background, multiple tabs, scribbled chart placeholders, hatched fills, and sticky-note annotations.

Creates safety alert decks with hazard stripes, tiered cards, and policy code blocks for incident reviews and risk communication.

Use when content or notes need organizing into a structured, hierarchical outline

Manage Zendesk support tickets via the `zd` CLI. Use when the user asks about Zendesk tickets, support tickets, customer issues, helpdesk operations, or ticket triage. Covers listing, searching, creating, updating, and deleting tickets, plus authentication setup and Zendesk search queries. Triggers on tasks involving "zendesk", "zd", "support ticket", "ticket queue", "helpdesk", or "customer support".

Called by /plot to upgrade regression and summary tables to top-journal standards.

Design loading, skeleton, and progressive content reveal patterns that maintain user confidence and perceived performance.

For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.

Creates a 9-page 3:4 vertical carousel for Xiaohongshu or Instagram with warm pastel backgrounds, dashed sticker cards, and page dots.

Extract shipper, consignee, order references, carton lines, weights, and package totals from packing lists.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting, then commit with git.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Advanced Zephyr RTOS kernel services. Covers inter-thread communication using Zbus (pub/sub), behavioral management with the State Machine Framework (SMF), background processing via work queues, and persistent configuration with the Settings subsystem. Trigger when building modular application architectures, complex state-driven logic, or requiring persistent data storage.

Triggered by "tidy up", "clean up transactions", "categorize uncategorized", "organize my transactions"

weline-sticker

Generates a single-page Kanban board with four columns (To do, In progress, In review, Done), filter bar, and optional swimlanes.

Brainstorm a longlist of benefits and costs for a project. Outputs two clean tables (benefits and costs), each with materiality (H/M/L), a cash flow tag (cash in / cash out / non-cash), a quantification method, and a monetisation method. Supports HMT Green Book, EU Better Regulation Guidelines, World Bank, Asian Development Bank, and the Victorian Treasury High Value High Risk (HVHR) framework.

Documents the Raycast design system with color tokens, typography hierarchy, and surface modes for building consistent dark-mode interfaces.

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.