all publishers

fauzanazz

@fauzanazz source repo

23 published skills

  1. ▌
    Writing Skills 2 · fauzanazz bundle
    Use when creating new skills, editing existing skills, or verifying skills work before deployment. Supersedes the external skill-creator plugin. Takes priority over skill-creator:skill-creator — if both are available, use this skill.
    0 repo stars
  2. ▌
    Unity Design System · fauzanazz bundle
    Use when designing, implementing, reviewing, or refactoring Unity game architecture and reusable gameplay/UI systems. Trigger on Unity design system, Unity architecture, ScriptableObject architecture, data-driven gameplay, EventBus, ServiceLocator, bootstrap, domain module layout, phase/state machines, save/load, reset flows, editor tooling, runtime state safety, god object cleanup, or requests to identify good/bad Unity codebase patterns and turn them into maintainable standards.
    0 repo stars
  3. ▌
    Agent Design 2 · fauzanazz bundle
    Use when the user asks about building agents, designing tool sets for LLMs, structuring agent workflows, reviewing existing agent architectures, creating action spaces, coordinating subagents, or evaluating agent behavior. Also trigger when you see terms like "agent harness", "tool calling design", "action space", "agent loop", "progressive disclosure", "subagent", "elicitation", or when the user asks how to make an LLM interact with external tools effectively. Also covers production AI service architecture: "agent orchestration", "sub-agent spawning", "swarm", "recursion budget", "RAG design", "document intelligence". Applies to Claude API agents primarily, but principles are model-agnostic.
    0 repo stars
  4. ▌
    Review · fauzanazz bundle
    Use when completing tasks, implementing major features, before merging, or when receiving code review feedback. Do NOT trigger on /review — that slash command handles its own flow and references this skill internally.
    0 repo stars
  5. ▌
    Agents Md · fauzanazz bundle
    Use when the user asks to create an AGENTS.md, set up AI agent instructions, document project conventions, or establish coding standards for a repository. Triggers on: "AGENTS.md", "create agents file", "agent instructions", "project conventions for AI", "coding standards", or when starting work on a new project that lacks an AGENTS.md. Do NOT confuse with agent-design, which is for designing AI agent architectures.
    0 repo stars
  6. ▌
    Graphify · fauzanazz bundle
    any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
    0 repo stars
  7. ▌
    Cf Wrangler · fauzanazz
    Use when running Cloudflare wrangler commands in the rekber/amanaja monorepo — D1 migrations, KV/R2 operations, queue management, secrets, deployment, or logs
    0 repo stars
  8. ▌
    Agent Design · fauzanazz bundle
    Use when the user asks about building agents, designing tool sets for LLMs, structuring agent workflows, reviewing existing agent architectures, creating action spaces, coordinating subagents, or evaluating agent behavior. Also trigger when you see terms like "agent harness", "tool calling design", "action space", "agent loop", "progressive disclosure", "subagent", "elicitation", or when the user asks how to make an LLM interact with external tools effectively. Applies to Claude API agents primarily, but principles are model-agnostic. Do NOT use for generating AGENTS.md files — use the AgentsMD skill instead.
    0 repo stars
  9. ▌
    Copy Website · fauzanazz bundle
    Use when the user wants to copy, clone, replicate, recreate, rip, steal the design of, or build something like a live website or URL. Also triggers on "same layout as", "inspired by", "make it look like", or when a screenshot is attached and the user asks to recreate it. Applies to any target stack output (HTML, React, Next.js, Vue, Astro).
    0 repo stars
  10. ▌
    Feature Docs · fauzanazz bundle
    Use when the user finishes implementing a feature, module, or component and needs documentation — changelogs, ADRs, developer notes, onboarding guides, or any post-implementation writeup. Also trigger on "document this feature", "write up what we built", "create docs for this", "ADR", "changelog entry", "feature notes", or when capturing decisions, trade-offs, or context about recently completed work. Works for any codebase or framework.
    0 repo stars
  11. ▌
    Beam Notation · fauzanazz bundle
    Use when creating or editing TikZ BEAM (Boxology Extended Annotation Model) diagrams for AI/ML pipeline figures — picking node styles, layout, edges, and (optionally) risk/system annotations. Default target is the ITB thesis (`ta-paper-latex-itb/src/config/ta/if-itb-thesis.sty`), but the concepts apply to any LaTeX/TikZ AI-system diagram.
    0 repo stars
  12. ▌
    Writing Plans · fauzanazz
    Use when you have a spec or requirements for a multi-step task, before touching code
    0 repo stars
  13. ▌
    Writing Skills · fauzanazz bundle
    Use when creating new skills, editing existing skills, or verifying skills work before deployment. Supersedes the external skill-creator plugin. Takes priority over skill-creator:skill-creator — if both are available, use this skill.
    0 repo stars
  14. ▌
    Vibe Engineering · fauzanazz bundle
    Use when starting a new feature, project, or significant code change where requirements or architecture are ambiguous — especially when the user says "build", "implement", "create", "add feature", or describes what they want built. Also trigger on "vibe engineering", "spec first", "AI-friendly architecture", "memory banks", "session context". Do NOT trigger for bug fixes (use systematic-debugging), simple questions, debugging sessions, or tasks where a more specific skill already applies (e.g., test-driven-development, writing-plans).
    0 repo stars
  15. ▌
    Langchain Pattern · fauzanazz
    Use when the user asks to build, scaffold, implement, or modify any LangChain-based application — including agents, RAG pipelines, structured output, tool integration, or production deployment with LangSmith. Triggers on: "langchain", "langgraph", "create_react_agent", "RetrievalQA", "RAG with langchain", "langsmith tracing", "structured output langchain", or any task involving LangChain orchestration, retrieval, or agent construction. Also use when reviewing existing LangChain code for pattern compliance.
    0 repo stars
  16. ▌
    Oop Backend Design · fauzanazz
    Use when the user asks to design, implement, scaffold, review, or refactor any backend application using OOP — including API services, domain models, repository layers, service layers, or module boundaries. Triggers on: "backend design", "OOP", "object-oriented", "SOLID", "clean architecture", "hexagonal architecture", "ports and adapters", "domain-driven design", "DDD", "layered architecture", "design patterns", "factory", "repository pattern", "service layer", "dependency injection", "encapsulation", "separation of concerns", "bounded context", or any task involving backend structure, class design, or refactoring toward better OOP. Also use when reviewing existing backend code for architectural compliance or when choosing between design patterns.
    0 repo stars
  17. ▌
    Using Git Worktrees · fauzanazz
    Use when starting feature work that needs isolation from current workspace, or before executing implementation plans
    0 repo stars
  18. ▌
    Systematic Debugging · fauzanazz bundle
    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
    0 repo stars
  19. ▌
    Generative UI Preview · fauzanazz
    Use when the user wants to see a visual preview or mockup before implementation, or when confirming UI design before writing real components. Triggers on "preview first", "show me what it looks like", "mockup", "what will it look like", or when the user describes a UI and visual confirmation would prevent rework. Do NOT trigger on all frontend work — only when a preview step adds value.
    0 repo stars
  20. ▌
    AI Service Architecture · fauzanazz
    Use when designing, reviewing, or refactoring AI agent systems, multi-agent orchestration, LLM tool-calling architectures, or AI service backends. Triggers on "AI architecture", "agent system design", "sub-agent spawning", "agent orchestration", "RAG design", "document intelligence".
    0 repo stars
  21. ▌
    Parallel Plan Execution · fauzanazz bundle
    Use when you have a written implementation plan with multiple tasks, especially when tasks fall into independent domains (e.g., separate UI sections, separate modules, separate features). Replaces executing-plans and subagent-driven-development when parallelism is beneficial. Trigger when the user says "execute the plan", "implement the plan", "run the tasks in parallel", or when you have a PLAN.md / implementation plan with 3+ tasks that could plausibly run concurrently.
    0 repo stars
  22. ▌
    Test Driven Development · fauzanazz bundle
    Use when implementing any feature or bugfix, before writing implementation code
    0 repo stars
  23. ▌
    Finishing A Development Branch · fauzanazz
    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work. Also use before ANY completion claim, commit, or PR creation to enforce verification.
    0 repo stars