all publishers

Tanq16

@tanq16 source repo

35 published skills

  1. ▌
    Agents Md · tanq16
    Writes and edits the rules in an instruction file, whether that is `AGENTS.md`, the `CLAUDE.md` symlinked to it, or a preset's `AGENTS.partial.md`. Covers the bullet a rule lands as, how its reason and its exception attach, which rules earn a place, where a new one goes, and when a rule replaces an existing bullet instead of joining it. Invoked explicitly as `/agents-md <the rule or the change>`, and applies on its own whenever the deliverable is a rule in one of those files. Not for a skill body, which `skill-creator` owns, and not for a standalone document, which `write-document` owns.
    3 repo stars
  2. ▌
    Skill Creator · tanq16
    User-invoked skill author. Writes a new skill (frontmatter, body, and any reference files) in the Agent Skills format and sized to fit the per-skill context budget. Invoked explicitly as `/skill-creator <what the skill should cover>`. It is not for editing an existing SKILL.md and does not decide whether an oversized skill should be split.
    3 repo stars
  3. ▌
    Write Document · tanq16
    Settles what a standalone document should be before it is written: whether a file is the right output at all, who consumes it (an agent, a third party, or the user), and which shape that consumer needs. Defers section order and house format to a more specific document skill whenever the session has one for that artifact. Invoked explicitly as `/write-document`, and applies on its own whenever a standalone document, plan, spec, handoff, analysis, report, runbook, or writeup is the deliverable. Not for chat replies, commit messages, PR bodies, or code comments, which the project's instruction files already govern.
    3 repo stars
  4. ▌
    Session Summary · tanq16
    User-invoked session handoff. `/session-summary pause` writes a structured resume file capturing what the session was doing, what changed, what was decided, and what is unfinished, folding any summary already there into a shorter form above it. `/session-summary resume` reads that file back and reports it as a few bullets, without starting any work it names. Invoked explicitly by name only. Never write or read the resume file on your own initiative, and never at the end of an ordinary task.
    3 repo stars
  5. ▌
    Develop · tanq16
    The entry point for any coding work in a project that has these skills installed - implementing a feature, changing or refactoring code, fixing a bug, scaffolding something new, or touching build and CI. Selects and loads the skills that govern the task before any code is written, holds the work to them while coding, and ends with a self-review of the diff against them. Use this first whenever you are about to develop anything. Not for a pure question with no code change, not for writing unit tests, and not for a full audit of an existing codebase.
    3 repo stars
  6. ▌
    Dockerize · tanq16
    Containerizing any project - multi-stage builds, choosing a base image, packaging the runtime, clearing package-manager caches, and running as a non-root user. Use when writing or changing a Dockerfile, picking a base image, deciding between alpine and debian-slim, building an image for more than one architecture, adding a docker-compose file, or when a container runs as root. Triggers on Dockerfile, docker-compose.yaml, FROM, multi-stage builds, buildx, BUILDPLATFORM, TARGETARCH, apk add, apt-get install, USER, adduser, groupadd, ENTRYPOINT, EXPOSE, musl, and glibc.
    3 repo stars
  7. ▌
    Go Idioms · tanq16
    Modern Go 1.27+ idioms and dependency selection, applied to every Go file written or reviewed. Use when writing or refactoring any Go code, when reading or writing JSON, when choosing between a standard-library helper and a hand-rolled loop, or when adding, auditing, or upgrading a dependency in go.mod. Triggers on interface{}, wg.Add, errors.As, atomic.LoadInt32, manual index loops, sync.Once, time.Now().Sub, encoding/json, json.MarshalIndent, json.NewDecoder, google/uuid, and on any go.mod change.
    3 repo stars
  8. ▌
    Node Auth · tanq16
    Password and session-cookie authentication for a Node Web Only server, built entirely on node:crypto. Use when adding a login flow, hashing or verifying a password, issuing or validating a session, setting a cookie, or protecting a route. Triggers on scrypt, timingSafeEqual, createHmac, Set-Cookie, HttpOnly, SameSite, users.json, session tokens, and any mention of bcrypt, jsonwebtoken, or passport.
    3 repo stars
  9. ▌
    Go Makefile · tanq16
    The Makefile for a Go project - pinned asset downloads, build targets with ldflags version injection, docker targets, and the semver version calculation. Use when creating or changing a Makefile, adding an asset to download, wiring a build for another platform, or working out how the release version is computed. Triggers on Makefile, make assets, make build-all, GOOS, GOARCH, CGO_ENABLED, ldflags, AppVersion, and the version target.
    3 repo stars
  10. ▌
    Node Idioms · tanq16
    Modern Node 24+ idioms and dependency selection - pure ESM, node: builtins, top-level await, structuredClone, AbortController. Use when writing or refactoring any Node code, or when adding, auditing, or upgrading a dependency in package.json. Triggers on require, module.exports, __dirname, import.meta, node: prefixed imports, JSON.parse(JSON.stringify()), fetch timeouts, AbortSignal, and any package.json dependency change.
    3 repo stars
  11. ▌
    Review Code · tanq16 bundle
    A thorough multi-agent audit of an existing codebase against the development skills, with one sub-agent per domain. Use when re-engaging a project you have not touched recently, when the skills may have changed since the code was written, when auditing a specific package or domain, or when a deliberate compliance pass is wanted. Not for checking the diff you just wrote, which the develop skill already covers. Accepts an optional target: a domain keyword such as cli, node, infra, or concurrency, or a package path such as internal/server.
    3 repo stars
  12. ▌
    Go OAUTH CLI · tanq16
    OAuth2 login for a Go CLI client, with three explicit modes and cached token refresh. Use when a CLI tool authenticates against Google, GitHub, Microsoft, or another OAuth2 provider, when building internal/auth/, or when adding a login command. Triggers on golang.org/x/oauth2, AuthCodeURL, config.Exchange, DeviceAuth, DeviceAccessToken, TokenSource, token.json, credentials.json, --device-login, and --manual. Not for server-side web OAuth where the browser stays on your own site.
    3 repo stars
  13. ▌
    Go CLI Output · tanq16
    The utils printer for Go CLI tools - the two output tiers behind --debug, the Print* API, table rendering, terminal colors, and error discipline. Use when writing anything a CLI prints, when building or changing utils/printer.go, utils/table.go, or utils/globals.go, or when a command reaches for fmt.Println. Triggers on PrintInfo, PrintSuccess, PrintError, PrintFatal, PrintWarn, PrintGeneric, PrintTable, GlobalDebugFlag, StdoutIsTerminal, lipgloss.Println, and lipgloss.ANSIColor.
    3 repo stars
  14. ▌
    Node Frontend · tanq16
    The vanilla-JS single-page frontend served from public/ by a Node Web Only backend - HTML structure, the Tailwind browser build, self-hosted fonts, the Catppuccin Mocha theme, and the reconnecting WebSocket client. Use when building or changing that page, laying out public/, theming it, choosing which surface a panel or control sits on, or wiring realtime updates. Triggers on public/index.html, public/js/, public/css/, public/vendor/, @font-face, @theme, crust, new WebSocket, reconnect backoff, and Catppuccin. Not for React, Vue, or Svelte, and not for a bundler-driven build.
    3 repo stars
  15. ▌
    Node Makefile · tanq16
    The Makefile for a Node Web Only project - vendoring pinned frontend assets into public/, compiling a native addon from source, verifying it loads, and the semver version calculation. Use when creating or changing the Makefile, adding a vendored asset, or wiring the native addon build. Triggers on make vendor, make verify, make setup, npm ci, npm_config_build_from_source, node-gyp, fnm, uv tool run, and fonttools woff2 compression.
    3 repo stars
  16. ▌
    Go CLI Prompts · tanq16
    Interactive input for Go CLI tools - when a prompt is the right channel at all, how a value resolves from a flag then stdin then a prompt, the shared stdin resolver behind a flag given -, the utils prompt helpers, and the ErrNoTerminal contract that keeps every command scriptable. Use when a command needs to ask the user something, when building or changing utils/input.go, when piping a secret or a file into a command, or when adding a password, free-text, or selection prompt. Triggers on PromptInput, PromptPassword, PromptTextArea, PromptSelect, PromptMultiSelect, ResolveStdin, MarkStdinLine, MarkStdinStream, SetAnnotation, ErrNoTerminal, StdinIsTerminal, a flag whose value is -, bubbletea textinput, and textarea.
    3 repo stars
  17. ▌
    Go Concurrency · tanq16
    Goroutine patterns for Go - WaitGroup, errgroup, bounded concurrency, fan-out/fan-in, and context cancellation. Use when running work concurrently, limiting how much runs at once, collecting results or errors from parallel operations, or making a long operation cancellable. Triggers on go func, sync.WaitGroup, wg.Go, errgroup, SetLimit, buffered channel semaphores, ctx.Done, and worker pools.
    3 repo stars
  18. ▌
    Go HTTP Server · tanq16
    The canonical net/http server for Go web services, with an embedded static frontend. Use when creating internal/server/server.go, serving a frontend out of the binary, adding a route or an API handler, or adding middleware. Triggers on net/http, http.ServeMux, go:embed static, embed.FS, fs.Sub, http.StripPrefix, http.FileServer, ListenAndServe, and any mention of gin, chi, or echo.
    3 repo stars
  19. ▌
    Project Readme · tanq16
    README structure for every project type: the frozen header block, the opener, and the rules that decide which sections a project earns and how long each one gets. Covers install paths including the self-hosted Docker run and compose blocks, collapsed tabular screenshots, and the test for when a section becomes its own file under docs/. Use when creating a README, restructuring one, deciding whether something belongs in the README at all, adding badges or navigation links, or documenting installation and configuration. Triggers on README.md, shields.io badges, .github/assets/logo.svg, a capabilities table, an install section, a docker-compose snippet, and screenshots of a web UI.
    3 repo stars
  20. ▌
    Go CLI Commands · tanq16
    The surface a Go CLI command exposes - the baseline every tool starts at, the two purchases on top of it, flag conventions, positional arguments, enum flags, a file-shaped value, and a flag that reads stdin. Use when adding or changing a flag, deciding whether a value should be a flag, a prompt, or a pipe, naming a value that spans lines, declaring Args, or validating a fixed set of allowed values. Triggers on PersistentFlags, BoolVar, StringVarP, SortFlags, cobra.NoArgs, ExactArgs, RangeArgs, pflag.Value, MarkFlagRequired, MarkFlagsOneRequired, MarkFlagsRequiredTogether, MarkFlagsMutuallyExclusive, MarkStdinLine, MarkStdinStream, and a flag whose value is -. Not for the shape of the command tree itself.
    3 repo stars
  21. ▌
    Go CLI Progress · tanq16
    Sequential running/done progress for Go CLI tools - phase, single-operation, multi-step, and check lifecycles plus the in-place progress bar. Use when a command runs a series of steps and should show what it is doing, when clearing terminal lines, or when adding a percentage bar. Triggers on PrintRunning, PrintIndentedSuccess, PrintIndentedError, ClearLines, ClearPreviousLine, PrintProgress, StdoutIsTerminal, and any command that prints "Running..." then replaces it with a result.
    3 repo stars
  22. ▌
    Go Job Pipeline · tanq16
    The Highway pattern - a resumable multi-job pipeline for Go CLI tools, with worker lanes, a UI-agnostic progress channel, and Ctrl+C resume. Use when a CLI processes many items through one pipeline (downloads, scans, migrations), needs configurable worker counts, needs progress that can drive a terminal or a web UI, or needs to pick up where an interrupt left off. Triggers on internal/highway/, internal/display/, internal/jobs/, a Job interface, a Progress channel, RegisterType, LoadState, and a resume command.
    3 repo stars
  23. ▌
    Chrome Extension · tanq16
    Chrome extension structure, Manifest V3, the popup, content scripts, service workers, and storage. Use when creating an extension, editing manifest.json, adding a permission, building the popup UI, injecting a content script, or wiring message passing. Triggers on manifest.json with manifest_version, chrome.tabs, chrome.scripting, chrome.storage, chrome.runtime.onMessage, service-worker.js, popup.html, and loading an unpacked extension.
    3 repo stars
  24. ▌
    Go CLI Structure · tanq16
    The shape of a Go CLI's command tree - main.go, the root command for each project type, Execute and the exit path, a command file, the Run body, Run against RunE, and subcommand packages. Use when scaffolding a Go CLI, writing or changing cmd/root.go, adding a command file or a subcommand package, wiring setupLogs and --debug, or deciding whether a command returns an error. Triggers on main.go, cmd/root.go, cobra.Command, rootCmd, Execute, AddCommand, cobra.OnInitialize, setupLogs, CompletionOptions, SetHelpCommand, SilenceErrors, SilenceUsage, Run, RunE, cmd/ packages, and AppVersion ldflags injection. Not for flag conventions, positional arguments, or a flag reading stdin.
    3 repo stars
  25. ▌
    Write Unit Tests · tanq16
    Writes unit tests, and only when the user has asked for them. Invoked as /write-unit-tests <scope>, or when the user asks in their own words for unit tests to be written or an existing suite extended. Reads the source in scope, separates business logic from helper code, selects only the edge cases and unwanted behaviors worth pinning, holds the plan under an estimated-coverage ceiling, then writes the Go or Node tests. Nothing else starts it: a feature landing, a bug fix, a refactor, a PR being prepared, and a _test.go or *.test.js file sitting in the diff are not requests for tests. Also the reference a code review reads when auditing an existing suite.
    3 repo stars
  26. ▌
    Go Project Layout · tanq16
    The canonical Go project taxonomy, directory layout, logging discipline, the config directory, and config loading. Use when starting a Go project, adding a package or directory, deciding where a file belongs, wiring zerolog, or deciding where a tool keeps its config and credentials. Triggers on go.mod, main.go, cmd/, internal/, pkg/, utils/, internal/server/static/, setupLogs, ConsoleWriter, ~/.config, and on any question of whether a project is CLI Only, Web Only, CLI + Web, a Headless API Service, or a Library.
    3 repo stars
  27. ▌
    Node Config State · tanq16
    Config layering and durable state for a Node Web Only server - defaults deep-merged with config.json, the ephemeral session secret, and atomic state.json writes. Use when loading config, adding a config key, deciding what may be persisted, or writing a state file. Triggers on config.json, config.example.json, deepMerge, loadConfig, state.json, randomBytes session secrets, mode 0600, and write-then-rename.
    3 repo stars
  28. ▌
    Node HTTP Ws Server · tanq16
    The node:http plus ws server for a Node Web Only project - src/ module layout, routing, static serving from public/, the WebSocket upgrade, broadcast, and graceful shutdown. Use when building or changing the backend server, adding a route or an API endpoint, serving the frontend, handling realtime messages, or deciding where an error is caught. Triggers on createServer, WebSocketServer, noServer, server.on('upgrade'), wss.handleUpgrade, serveStatic, path traversal guards, SIGTERM, and process.exit.
    3 repo stars
  29. ▌
    Node Project Layout · tanq16
    The Node Web Only project shape - directory layout, package.json, the thin bin/ launcher, and console logging. Use when starting a Node project, deciding where a module belongs, writing package.json or .node-version, or emitting a log line. Triggers on "type":"module", engines node >=24, .node-version, bin/, src/, public/, test/, config.example.json, and console.log with level prefixes.
    3 repo stars
  30. ▌
    Go Embedded Frontend · tanq16
    A single-page frontend embedded into a Go binary from internal/server/static/ - HTML boilerplate, Tailwind v4 browser build, the Catppuccin Mocha palette, self-hosted fonts, icons, and PWA files. Use when building or changing the web UI of a Go Web Only or CLI + Web project, laying out static assets, theming a page, choosing which surface a panel or control sits on, or adding PWA support. Triggers on internal/server/static/, index.html, tailwind, @theme, Catppuccin, crust, favicon, manifest.json, sw.js, Lucide, and Font Awesome. Not for templ or htmx server-rendered HTML, and not for a framework SPA built outside the repository.
    3 repo stars
  31. ▌
    Web Mermaid Diagrams · tanq16
    Catppuccin Mocha themed Mermaid diagrams in a browser page. Use when a frontend renders flowcharts, sequence diagrams, gantt charts, pie charts, git graphs, state diagrams, timelines, or mindmaps, or when Mermaid output does not match the page theme. Triggers on mermaid.initialize, mermaid.run, themeVariables, startOnLoad, a mermaid code fence, and diagrams rendering with default colors or on the wrong surface.
    3 repo stars
  32. ▌
    Node Release Artifacts · tanq16
    Choosing and building the release artifact for a Node Web Only project - a single self-contained binary or a runtime-bundled tarball. Use when deciding what a Node project ships, compiling with Bun or Node SEA, writing the bundle script or its launcher, or proving a bundle runs without a system Node. Triggers on bun build --compile, node --build-sea, sea-config.json, postject, scripts/bundle.sh, a runtime/bin/node layout, and a .tar.gz release asset.
    3 repo stars
  33. ▌
    Web Markdown Rendering · tanq16
    Rendering Markdown to styled HTML in a browser page with Marked, Highlight.js, and the Catppuccin palette. Use when a frontend displays notes, documentation, or any user-supplied Markdown, when adding syntax highlighting, callout blocks, or code copy buttons, or when styling rendered Markdown. Triggers on marked.parse, marked.use, hljs.highlight, .markdown-body, callout blockquotes such as [!TIP] and [!WARNING], and copy-to-clipboard buttons on code blocks.
    3 repo stars
  34. ▌
    Github Release Workflow · tanq16
    The GitHub Actions release workflow and the semver commit-marker convention. Use when creating or changing .github/workflows/release.yaml, adding a build job or a platform to the matrix, wiring container publishing, or working out how a release version is chosen. Triggers on release.yaml, gh release create, draft releases, actions/checkout, actions/setup-go, actions/setup-node, docker/login-action, docker/build-push-action, multi-arch image publishing, [minor-release], and [major-release].
    3 repo stars
  35. ▌
    Go Package Architecture · tanq16
    How internal/ packages are organized in a Go project and how errors travel across their boundaries. Use when creating a package under internal/, deciding between domain and layered organization, choosing where to wrap an error, designing a persistence layer, or shaping a config struct that a command fills from flags. Triggers on internal/ package creation, fmt.Errorf wrapping, Store interfaces, JSONStore, handlers/services/models directories, and http.Client construction.
    3 repo stars