Results for “ap-style”

Writes documents in a plain, human voice and removes phrasing that reads as machine-generated, applying a two-pass write-and-audit process to any written artifact meant to be read by a person.

Prose quality checker for Quarto (.qmd) files, grounded in William Zinsser's *On Writing Well* (30th Anniversary Edition). Checks for clutter, weak verbs, hollow qualifiers, clichés, inflated academic voice, poor leads and endings, pronoun and tense inconsistency, and unclear explanation. Produces a structured markdown report organized by document section — never modifies the source file. Use when asked to improve prose quality, tighten writing, reduce clutter, or apply Zinsser's writing principles to a draft. For grammar and punctuation, use the proofread skill. For APSA style rules, use the apsa-style skill. Supports an optional output-file argument and an optional @sec-label argument to restrict checking to one section.

Creates long-form magazine-style articles with hero sections, serif headings, styled quotes, code blocks, and call-to-action cards, suitable for Substack, Medium, or blogs.

Select a consistent visual design system for PPT slides using radius/spacing style recipes, including Sharp, Soft, Rounded, and Pill variants with component mappings and typography rules.

Design REST and GraphQL APIs with OpenAPI 3.1 specifications, resource modeling, versioning strategies, pagination patterns, and error handling standards.

Provides a creative-direction layer for music videos and short-form edits in the angelcore/cloud-trance/hyperpop visual family, encoding aesthetic vocabulary, mood/color/light system, and beat-synced editing grammar to produce intentional, stylistically coherent video content.

Expert at designing clean, consistent, and developer-friendly APIs. Covers RESTful conventions, versioning strategies, error handling, pagination, rate limiting, and OpenAPI documentation. Designs APIs that are intuitive to use and easy to evolve. Use when "API design, REST API, RESTful, API versioning, API documentation, OpenAPI, Swagger, API error handling, pagination, rate limiting, api, rest, http, versioning, pagination, openapi, swagger" mentioned.

Audits codebases, pages, or documents for AI-generated design and copy tells, then proposes surgical fixes for user approval.

Pulls pathway, book, course, article, and content item records from a Supabase database for the alan-hirsch tenant, organizes them by portal, and exports the results as markdown files into a local docs repository.

Guides contributors through adding, updating, publishing, documenting, validating, and wiring public skills in the BuilderIO/skills repository, covering plain skills, instruction-style skills, app-backed/MCP skills, and Plan skill sync.

Takes a proofread or apsa-style report file (or any markdown file using **Original:** / **Recommended:** syntax) and rewrites the original source file with git merge conflict markers so the user can accept or reject each suggested edit using VS Code or Positron's built-in merge conflict UI. Branch names are "original" and "claude-edits". Use when asked to apply edits, insert conflict markers, or set up merge resolution for a copy-edit report. Supports an optional @sec-label argument to restrict markers to one section.

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.