个人作者

ahmedfidi-cmyk

更新于 2026-10-27

Skills
37
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 0

ahmedfidi-cmyk 的 Skills 37

ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

writing-for-agents

Writing documents for agents. Use when creating or editing skills, modifying AGENTS.md or CLAUDE.md, or writing any doc an agent reaches by a pointer.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

what-would-you-do

Explain the question you just asked and recommend an answer, with the case for and against each option.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

wait-what

Stop. That last message did not land: re-pitch it.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

triage

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

to-questionnaire

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

teach

Teach the user a new skill or concept, within this workspace.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

ship-pr

Commit, push, open a pull request, wait for green CI, then squash merge and close the issues it finishes.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

setup-supermatt-skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

retro

Conduct a retrospective on a coding session.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

resolving-merge-conflicts

Resolves an in-progress git merge or rebase conflict by tracing why each side changed, reconciling every conflicted hunk, running the project's checks, and finishing the merge or rebase. Use when a merge, rebase, or pull stops on conflicts, when files contain conflict markers, or when the user asks to fix or resolve merge conflicts.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

refactor

Refactor code at method, file, or project scope. Assesses first and stops when the code is already clean, routes architecture problems elsewhere, and gates edits on test coverage. Language-agnostic.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

qa

QA a change in the running program, the way its user meets it: drive a CLI or terminal UI through tmux, a web app through a browser, and check every requested behavior against what you observe. Use after implementing a change and before code review, or when the user asks for a QA pass, a smoke test, or a click-through of a change, or asks whether it actually works.

★ 0
ahmedfidi-cmyk
ahmedfidi-cmyk/tims-backend

prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

★ 0