flungo

claude-code-web

Fabrizio's working preferences and hard constraints for Claude Code Web (the browser and cloud environment at claude.ai/code, as opposed to the local CLI). Consult this whenever a session runs in that environment and something behaves differently from local — outbound network going through the egress proxy, GitHub access, installing tools, adding or scoping repositories, setting environment variables or secrets, or a command that can't run in the sandbox and should be delegated to CI. Personal, always-on preferences; they complement a repo's own CLAUDE.md rather than overriding it.

docs-standards

Fabrizio's documentation conventions for a repository's docs/ tree. Consult this whenever writing or maintaining docs in one of his repos — adding or changing an ADR, plan, runbook, or reference doc; updating a README index; recording an architectural decision; retiring a completed plan; or scanning for stale docs at session end. Covers the Diátaxis directory split (decisions, plans, runbooks, reference), the Nygard ADR format, the ephemeral two-PR plan lifecycle, keeping every README index current in the same commit, the agent-directed and verify callouts, semantic line breaks, and a session-end doc-maintenance checklist. Complements the repo's own CLAUDE.md rather than overriding it.

contributor-workflow

Fabrizio's personal, named git/PR workflow commands — structured workflows he invokes by name for a particular task. Currently "/ready-to-merge" (aliases "Ready to Merge?", "RTM?"), a final pre-merge sweep of a PR covering title/description accuracy, review-thread triage, resolving fixable ambiguity, cleaning up commit history, and marking it ready. More commands expected over time. Relies on the git-conventions skill for the underlying git hygiene rules.

Code & Development Listed

git-conventions

Fabrizio's standing git/PR hygiene conventions. Consult this whenever making commits, creating or managing branches, rebasing, force-pushing, or opening/landing a PR in any repo he's working in — not just when a named command is invoked. These are his default rules (never commit to main, branch management, Conventional Commits, linear history, squash-vs-rebase, no fixup commits, force-push policy) and apply to ordinary git work generally, complementing rather than overriding whatever the repo's own CLAUDE.md/CONTRIBUTING.md says.

upstream-research

Fabrizio's method for researching and verifying facts about third-party and upstream components — a library, API, tool, provider, or service the project depends on. Consult this whenever you need to confirm how an external component actually behaves — its config options, API shape, wire format, an env var name, a version-specific change, or a bug — instead of relying on memory. The rule is to go to the authoritative source (the project's own repository and official docs), distrust training data, web-search summaries, and generated docs, and record where each fact came from. Personal, always-on; complements a repo's own CLAUDE.md.