Nisus74

Use this skill for any pencil.dev work, such as designing UI in a .pen file, editing an open Pencil canvas, sketching or mocking screens, instantiating components from a .lib.pen library, reading an existing design system from a .pen or .lib.pen file, fixing batch_design schema errors, or recovering from Pencil MCP host-not-connected issues. Pick it on any mention of pencil.dev, .pen, .lib.pen, "the Pencil MCP", "the Pencil canvas", or a design-system/ folder in a Pencil context, even when the user phrases it casually, mid-sentence, or doesn't name the tool. This is the canonical skill for all Pencil tasks; reach for it before any general design or frontend skill when Pencil signals are present.

Write, rewrite, edit and review human-facing prose in a specific person's voice. Use for emails, posts, reports, proposals, PRDs, board papers, documentation, applications, messages and any text the user will send, publish, present or sign off. Also use when the user asks for Australian English, natural writing, less corporate language, fewer AI tells, stronger voice, or prose that sounds like them. Do not apply the prose sweep to code, config, fixed legal text, quoted material or private scratch notes unless the user asks.