dear_bryan

Draft and submit my daily standup to Parabol from my git activity, then submit only on my explicit OK. Uses the `paracli` CLI (brew install itisbryan/tap/paracli) for all the work; this skill just drives it interactively. Use when I say "do my standup", "submit my daily report", or "post my Parabol update".

Turn an overwhelming idea into one shippable slice and one next action — so you start today instead of drowning in the plan. Use when you have an idea you want to build but the scope/plan is overwhelming, when you're stuck at "where do I even start", when a project has stalled, or when you can feel burnout coming from a plan that keeps growing. The opposite of a big plan — it shrinks, it doesn't expand.

Authorized web-application penetration testing — recon, vulnerability analysis, proof-based exploitation, and a professional report. "No exploit, no report" — every finding needs reproducible evidence. Hard guardrails for authorization, scope, and secret-leakage. Use when asked to "pentest [URL]", "security-test this web app", "find vulns in [URL]", or "OWASP-test" a running application the user owns or is authorized to test.

GitHub workflows via the gh CLI — a collection of subskills for issues, pull requests, and wikis. Loads the right subskill on demand. Use when asked to create or open an issue, ticket, bug report, or decision/spike; open a pull request or submit changes for review; review a pull request or respond to review feedback; check CI / GitHub Actions status and diagnose a failing run; fetch, view, or pull up an issue by number or URL; triage, label, assign, close, or link existing issues; or generate and publish a GitHub Wiki (docs + architecture/Mermaid diagrams) for a repo.

Guides distinctive, native-feeling macOS desktop app GUI design — recommends or lets you pick a Mac app archetype (system-native, pro/dense, content-first, menu-bar utility, prosumer-creative), then builds a real system of window chrome, materials, semantic colors, SF type, and native controls so the app reads as a real Mac app, not a web page in a window. Loads focused references (catalog, hig-structure, materials-color, typography, controls, motion-polish, anti-slop) on demand. Use when designing or restyling a macOS app UI in SwiftUI or AppKit, or when a Mac app "feels like Electron / like a website / not native."

Study a specific public repo to learn how they solve a problem — clone it, trace the real mechanism through code and tests, mine git history for the why, and write an evidence-cited learnings doc with what to adopt. Use when asked to "learn from repo X", "how does project Y do Z", "study this codebase", "what can we steal from", or "write a doc on how they built" something.

Turn a rough idea into an approved design before any code — explore intent, constraints, and 2-3 approaches through one-question-at-a-time dialogue, then write a design doc the user signs off on. Use before creating a feature, component, or behavior change, especially when a task seems "too simple to need a design."

Systematic exploratory QA of a running web app — navigate it, exercise the flows, capture evidence, and produce a severity-ranked bug report. Optionally files each finding as a structured issue via gh-workflow. Use when asked to QA, dogfood, smoke-test, or "find bugs in" a web app, page, or feature before shipping.

How I work with Rails — a growing collection of subskills covering my tooling, conventions, and workflows for Rails projects. Loads the relevant subskill on demand. Use when working in a Ruby on Rails codebase (setup, running the app, gems, Ruby versions, conventions). Currently ships use-rv (Ruby version & gem management with rv).

Acts as your personal coding tutor — teaches concepts, guides you to write your own code through Socratic questioning, reviews your attempts with targeted feedback, and adapts its style (Socratic → explanatory → pair-programming) based on your cues. NEVER writes your solution for you. Use when you want to learn, understand, practice, or be coached rather than have code written for you.

Guides distinctive, intentional web/UI design — recommends or lets you pick a direction, mirrors a specific site's design language, or does a pixel-perfect clone of a page you own ("make it look like Stripe / Linear", "clone this exactly"), then builds a real type/color/space system so the result looks decided-on, not defaulted-into. Loads focused references (catalog, mirror, clone, typography, color, layout, polish, anti-slop) on demand. Use when building or restyling a landing page, dashboard, portfolio, or any UI, or when a design "looks generic / templated / like AI made it."

Test-driven development — write the failing test first, watch it fail, write the minimal code to pass, then refactor. Enforces red-green-refactor for new features, bug fixes, refactors, and behavior changes. Use when building or changing behavior and you want the tests to drive the design, not trail behind it.

Systematic root-cause debugging — reproduce the bug with a tight red/green loop, trace it to the actual cause, and fix that, not the symptom. Use for any test failure, production bug, crash, unexpected behavior, performance problem, or build failure — especially under time pressure, or after a previous fix didn't hold.