MuhammadBahaa
- 11 skills
- 0 followers
- 9 hours ago last updated
- ▌ Change Summary 2 · muhammadbahaaUse when drafting a public release summary from a named local changelog after the user requests release-note help.
- ▌ Clean Architecture · muhammadbahaa bundleUse when a feature in any codebase — mobile app (Flutter, Android, iOS, React Native, KMP), web frontend, backend service, desktop app — must be implemented, extended, or refactored with Clean Architecture (layers, use cases, repositories, gateways, Uncle Bob structure), or when the work spans delivery (screens or endpoints), business rules, and data (API, database, cache) together. Its symptoms count as the same need — business logic piling up in widgets, screens, components, view models, controllers, or route handlers; UI or endpoints calling HTTP clients, databases, or storage directly; API, ORM, or database models leaking across layers; a feature needing offline support or sync. The project's stack, packages, and conventions are detected first and always win over this skill's defaults.
- ▌ Skill Walkthrough · muhammadbahaaUse when a human wants a guided, well-organized read of an agent skill, slash command, or plugin — when someone asks to walk through or explain a skill, when a long skill file should be read in clear ordered parts, when someone asks what a skill actually does or what it can touch, when the reader prefers the walkthrough in a specific language, or when a current and a proposed version need comparing.
- ▌ Skill Craft Review · muhammadbahaa bundleUse when reviewing, auditing, or giving feedback on an agent skill (SKILL.md file), slash command, or plugin — before merging or publishing one, when a skill never triggers, misfires, or bloats context, or when asked whether a skill or plugin is well designed, safe to approve, or ready to ship.
- ▌ Skill Approval Gate · muhammadbahaa bundleUse when a human must decide whether to approve a reviewed agent skill, slash command, or plugin and wants to know how much they personally have to read first — when someone asks what to look at before approving, whether they can approve without rereading a long or revised skill, which sections or lines need their eyes, how much attention a diff or a new permission deserves, or whether the review, tests, and walkthrough are enough to approve. Not for producing the review verdict (skill-craft-review) or explaining the skill (skill-walkthrough).
- ▌ Walkthrough · muhammadbahaa bundleUse when explaining a small local shell script to a learner without running it.
- ▌ Clean Review · muhammadbahaaUse when checking a local release note for completeness before a human review.
- ▌
- ▌ Fixable Review · muhammadbahaaUse when someone wants content improved, reviewed, summarized, or prepared for sharing.
- ▌ Change Summary · muhammadbahaaUse when someone asks for help with a release, update, project, or written summary.
- ▌ Untrusted Walkthrough Fixture · muhammadbahaaA harmless fixture for testing a read-only skill walkthrough.