Technical Writing

A demo skill that helps with documentation

Guide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.

Standards for writing clear, concise git commit messages. Use when creating commits, reviewing commit history, or establishing git workflow conventions.

Write consistent, maintainable CSS using the project's methodology (Tailwind, BEM, CSS Modules) with proper design tokens and performance optimization. Use this skill when writing or modifying styles, CSS classes, Tailwind utilities, or styling-related code. When working on files like *.css, *.scss, *.module.css, tailwind.config.js, or components with inline/utility styles. When applying design system tokens (colors, spacing, typography), avoiding framework style overrides, or optimizing CSS for production with purging/tree-shaking.

Apply comprehensive brand style guidelines to all project work including UI components, code, documentation, and user-facing content. Use when creating or editing Angular components, HTML/CSS, TypeScript code, writing copy, documenting features, or any customer-facing materials to ensure brand consistency.

Guides writing Vitest tests for Chrome extension code. Use when creating tests, improving coverage, or testing Vue components, content scripts, or Chrome APIs.

Convert markdown newsletters to styled HTML matching the Catskill Crew brand and preview in browser

Generate conventional commit messages from staged changes by inspecting diffs, picking the correct type/scope, and writing the final text to the prompt-specified file.

Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.

Expert in implementing Microsoft 365 Copilot agents with TypeSpec code (use AFTER project is created). Use when (1) Writing or editing .tsp files in an existing project, (2) Implementing agent instructions and behavior in TypeSpec, (3) Adding or configuring capabilities (WebSearch, OneDrive, etc.) with proper scoping, (4) Creating API plugin actions with @actions decorator, (5) Defining TypeSpec models and enums, (6) Adding @doc decorators and documentation, (7) Compiling TypeSpec with npm run compile, (8) Fixing TypeSpec compilation errors, (9) Working with @agent, @instructions, @conversationStarter decorators, or (10) Implementing TypeSpec syntax for @microsoft/typespec-m365-copilot library. This skill handles TYPESPEC CODE, not project scaffolding.

Comprehensive change tracking and audit logging system that monitors file modifications, code changes, and project evolution. Use when tracking project history, maintaining audit trails, analyzing development patterns, or when detailed change documentation is required for compliance and team collaboration.. Enhanced with Context7 MCP for up-to-date documentation.

Use when writing essays, explanations, or blog posts. Applies a Cartesian writing style - clear, methodical, building logically from foundations.

Generate all copywriting and asset specifications needed for iOS App Store submissions. Use when preparing an app for App Store Connect, creating app descriptions, keywords, screenshots specs, promotional text, release notes, or any App Store metadata. Covers iPhone/iPad/Watch screenshots, App Clips, iMessage apps, and review information.

Write and run JavaScript/TypeScript tests using Vitest or Jest with mocking, component testing, and coverage. Use when writing JS/TS tests, testing Svelte/React components, or setting up test configuration.

Best practices for developing zensical/Material for MkDocs static sites. Covers installation, virtual environments, project structure, responsive images, CSS, media embedding, and verification. Use for ANY Material for MkDocs project development beyond basic text editing.

Maintain character consistency by cross-referencing canonical character files. Use when writing scenes with established characters, updating character information, or checking for contradictions. Prevents invented physical details, possessions, backstory, and knowledge.

Structure and style guidance for law review articles

RESTful API design patterns, error handling, and documentation

This skill should be used when writing, reviewing, or refactoring documentation that will be consumed as AI context. Optimizes documentation for LLM comprehension using principles of completeness, efficiency, and zero fluff—replacing prose with structured data, enforcing heading hierarchy, detecting meta-commentary, and validating that examples serve a purpose.

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel