flungo
UserPersonal Claude Code / Claude.ai plugin marketplace
Categories
Indexed Skills (13)
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, and a session-end doc-maintenance checklist. Relies on the markdown-standards skill for how the Markdown itself is written. Complements the repo's own CLAUDE.md rather than overriding it.
markdown-standards
Fabrizio's Markdown authoring conventions. Consult this whenever writing or editing Markdown in one of his repos — adding or changing a link, cross-reference, or heading; fixing a markdownlint finding; fixing a failed link/anchor check (lychee) or a markdown-links external-sweep issue; deciding how to reference an ADR, file, or another repo; or onboarding a repo to the Markdown validation CI via /adopt-markdown-ci. Also consult it when a lint rule fires on content that was already there and previously passed, which a linter version bump can cause across every repo at once. Covers unambiguous cross-reference and link-text rules, semantic line breaks, unique cross-referenced headings, adjacent-blockquote handling, compact tables (delimiter rows included), handling lint rules a linter bump introduces, and fix-the-target-never-suppress remediation. Complements the repo's own CLAUDE.md rather than overriding it.
cloud-sessions
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, a plugin or a repo's adopted conventions not being loaded, or a command that can't run in the sandbox and should be delegated to CI. Always-on preferences; they complement a repo's own CLAUDE.md rather than overriding it.
personal-cloud-environment
The manually-applied configuration of Fabrizio's own Claude Code Web environment — its name, network allowlist, environment variables, and setup script — layered on top of the platform defaults. Consult this in a web session to know what is actually reachable or set before probing or working around it, whenever an allowlist or environment-variable change is proposed, and whenever Fabrizio says he has changed the environment, so the change is persisted back here. Companion to the environment-agnostic cloud-sessions skill.
handoff
Fabrizio's "/handoff" command — produces a session handoff document so a fresh Claude session can pick up exactly where this one left off. Use it whenever he says "handoff", "create a handoff", "session handoff", "new session", "summarise for next session", or anything else suggesting he wants to continue this work in a different conversation, including wanting to share context with a new agent, start fresh, or resume later. If in doubt and the conversation holds meaningful work, lean toward triggering.
session-clean
Fabrizio's "/session-clean" command (aliases "Session Clean?", "Safe to delete?") — a check on whether the current chat session can be closed or deleted without losing anything. Use it whenever he asks if a session is safe to close, safe to delete, done with, or finished, or invokes the command by name. It sweeps the whole conversation for work left undone, questions left unanswered, options left undecided, and facts or decisions that exist only in the chat, then proposes where each should be recorded. It never writes, commits, or files anything without his confirmation first.
terraform-standards
Fabrizio's conventions for writing and maintaining a Terraform/HCL configuration repository (a consumer of providers, not a provider itself). Consult this whenever adding or changing .tf files, naming resources, handling secrets in config, pinning a provider, or bringing an existing cloud resource under Terraform management. Repo-adopted (project scope) — a repo enables it in its .claude/settings.json; it complements, and defers to, that repo's own CLAUDE.md.
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.
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.
scaffolding
Fabrizio's guide for setting up, building out, and extending repos across his fleet. Use it when creating a repo, wiring up CI, bringing an existing repo up to standard, or deciding which of his conventions a repo should take on. The gate is ownership — a repo he owns (verified, not just in his namespace) adopts his conventions and standards plugins; a fork or third-party repo gets nothing adopted without his explicit consent. It routes to the shared CI in flungo/github-workflows and the helper repos (github-workflows, claude-plugins, terraform-github) you add_repo as needed. Personal (user scope) — always on for his account.
terraform-provider-standards
Fabrizio's conventions for building a Terraform provider in Go — the terraform-plugin-framework layout, tfplugindocs-generated docs, MPL-2.0 per-file headers, and adopting the shared flungo/github-workflows provider CI (golangci-lint v2, GoReleaser dual-registry release). Consult it whenever writing or changing a terraform-provider-* repo, whether the provider's resources and data sources, docs generation, tests, CI, or release. Repo-adopted (project scope) — a repo enables it in its .claude/settings.json; it complements, and defers to, that repo's own CLAUDE.md, and pairs with git-conventions and docs-standards.
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. Also consult it before reporting a commit signature or "Unverified" warning, which is usually expected and not actionable. These are his default rules (never commit to main, branch management, Conventional Commits, linear history, squash-vs-rebase, no fixup commits, force-push policy, signature-warning handling) and apply to ordinary git work generally, complementing rather than overriding whatever the repo's own CLAUDE.md/CONTRIBUTING.md says.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.