Showing 45631–45660 of 77205 skills
Applies dependency-direction rules when writing or reviewing Go code — consumer-defined minimal interfaces, no domain→infrastructure imports, one-way package arrows. Load whenever writing, refactoring, or reviewing Go packages, designing package layout, defining interfaces, or wiring repository/service/handler layers.
rgglez/rgglez-dev-skills
Applies dependency-direction rules when writing or reviewing Go code — consumer-defined minimal interfaces, no domain→infrastructure imports, one-way package arrows. Load whenever writing, refactoring, or reviewing Go packages, designing package layout, defining interfaces, or wiring repository/service/handler layers.
rgglez/rgglez-dev-skills
Research and write professional newsletters.
HezaoHezao/poirot
Sync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the user runs /git-sync or says "git-sync", "sync", "commit and push", "pull and push", or "sync my branch".
zzsoszz/ai-software-factory
Builder lane of the super-board pipeline — takes a `Ready` GitHub Project card into its own per-issue git worktree, makes the smallest safe change test-first (TDD, `ponytail` simplest-first, official docs first for third-party APIs, upgrades and auth/billing), opens a draft PR and hands it to QA and Review through the board; it never merges — merges go through the Reviewer's merge gate. Inside `super-board run` it runs as a lane agent in the in-session wave workflow (`workflows/super-board-wave.js`, no worker cap unless `max_workers` is set); standalone headless `claude -p` dispatch is legacy opt-in. Use when the user says "Super Build", "run the build loop", "/super-build", or invokes the skill.
zzsoszz/ai-software-factory
Find problems in one project, verify each, write one findings doc and hand it to Matt Pocock's /to-spec then /to-tickets; 1–5 tickets go to /implement-spec, 6+ to the super-board Backlog (no /to-spec or /to-tickets installed → files straight into Backlog). Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier first. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors".
zzsoszz/ai-software-factory
Super QA canonical workflow for functional bug-bash, evidence capture, and fix-ready issue filing. Crawls routes from `docs/super-qa/queue.md` with Playwright, records screenshots/logs/HARs, files product-readable issues with clear type/priority/area labels, and continues until traversal is complete or only human-gated blockers remain. Crawling is always browser-driven, but the regression test it leaves behind is written at whichever layer the defect actually lives — unit or integration in Vitest, e2e in Playwright only when the browser is the thing that broke. Use when the user says "run super-qa", "QA review", "bug bash", "verify and fix", or invokes `/super-qa`.
zzsoszz/ai-software-factory
Reviewer lane of the super-board pipeline and standalone PR/branch readiness review — forms its own hypotheses before reading the builder's summary, remembers prior findings and re-checks each with file:line proof, runs an adversarial truth-check on non-trivial diffs, and classes every finding (Gap, Bug, Verification miss, Scope drift, Over-engineering via `ponytail:ponytail-review`). Merges only through `super-board-merge-gate.sh`, pinned to the reviewed head SHA, and routes other fixes to Super Build or Super QA via the board. Use when the user says "Super Review", "review this branch", "review loop", "make sure this is merge-ready", "PR review", or asks for code, architecture, security, QA evidence, or release-readiness judgment.
zzsoszz/ai-software-factory
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
zzsoszz/ai-software-factory
Use for paranoid, language-agnostic architectural code review — applies SOLID, DRY/KISS/YAGNI, decoupling, OWASP/NIST security, and quantitative complexity thresholds (cyclomatic > 15 fails) via the ADIHQ framework. Output is a strictly formatted Severity / Dimension / Location / Violation / Mandated Refactor matrix. Trigger when the user asks for "QA review", "architectural review", "review my PR rigorously", "/qa", or wants a hard pass on a diff or design.
joedaws/agent-techniques
Design Forge's Phase 4B deep-research subsystem so every claim in a generated report traces to a fetched source. Load when building or reviewing a multi-source research agent, planner/executor separation, parallel subagent fan-out, source adapters over src/scraping/ tiers, citation verification, claim-level entailment or faithfulness checks, hard-fail on unverifiable citations, report artifacts in Tigris, context-budget management for long syntheses, per-request cost caps for research aliases, or any request shaped as 'add deep research' / 'generate a cited report' / 'why are the citations wrong'.
opensite-ai/opensite-skills
Read actively and take useful notes: a purpose and questions, previewing, reading depths from skim to study, questioning the text, recall instead of rereading, notes in your own words, accurate quotes and sources, summaries, linking notes to projects and reviewing them. Use whenever someone wants to read books, papers or reports more effectively, take better notes, remember what they read, summarise a book or turn reading into useful knowledge.
afeezadebayo/research-learning-skills
Use AI research tools well: choosing between deep research modes, AI search, assistants and browsing agents, writing research briefs with preferred sources and evidence standards, verifying citations, filling gaps, resolving conflicts, protecting confidential data and writing a human-checked synthesis. Use whenever someone uses deep research, AI search or an AI agent to research a topic, wants better research prompts, needs to verify AI-cited sources or turn an AI research report into a reliable summary.
afeezadebayo/research-learning-skills
Run effective desk research: search terms from sub-questions, source types from official statistics to filings and studies, search operators, primary sources, skimming and reading, lateral credibility checks, a research log, tracing citations, triangulation and summaries of what is known, uncertain and unknown. Use whenever someone needs to research a topic online, find statistics or market data, search for regulations or company information, trace a statistic to its source or build a research log.
afeezadebayo/research-learning-skills
Plan and run customer, user, buyer, churn and expert interviews: learning goals, recruiting by behaviour, discussion guides with past-behaviour questions, good versus leading questions, consent and recording, note-taking, debriefs, expert interview tips and handover to synthesis. Use whenever someone needs to interview customers, users, prospects or experts, write an interview guide, run win-loss or churn interviews, recruit participants or avoid leading questions in research.
afeezadebayo/research-learning-skills
Learn by explaining: self-explanation research and the Feynman technique, explaining without notes, finding and studying gaps, plain-language rewrites, examples and non-examples, analogies with limits, teaching others, explanation templates and using AI as a questioning partner. Use whenever someone wants to understand a concept deeply, use the Feynman technique, check their understanding, prepare to teach or explain a topic, write an explainer or learn faster with AI quizzing.
afeezadebayo/research-learning-skills
Fact-check documents, decks, articles and AI outputs: extracting every claim, prioritising by risk, verifying against primary sources, recalculating numbers and units, confirming names, dates and quotes, spotting misleading-but-true framing, fixing wording and keeping a fact-check log. Use whenever someone needs to fact-check a report, article, pitch, social post or AI-generated text, verify statistics or quotes, check numbers before publishing or confirm that citations say what is claimed.
afeezadebayo/research-learning-skills
Build learning plans that work: testable target performances, starting assessments, sub-skills, focused resources, deliberate practice with feedback, real projects, weekly schedules, retrieval practice, spacing and interleaving, progress checks and adjustments, with a 12-week example. Use whenever someone wants to learn a new skill, tool, language or subject, plan study for a certification, change careers, build a learning roadmap or learn faster with practice instead of passive courses.
afeezadebayo/research-learning-skills
Review research evidence for work and study questions: question framing and inclusion criteria, review types from quick scans to systematic reviews, database searching and search strings, screening, data extraction, quality assessment, synthesis by theme and write-ups with confidence and gaps. Use whenever someone needs to know what research says about a topic, run a rapid evidence review, find academic studies, summarise papers, check a claim about a study or write an evidence-based recommendation.
afeezadebayo/research-learning-skills
Plan research before searching: the decision it serves, a sharp bounded question, an issue tree of sub-questions, hypotheses, depth matched to stakes, methods from desk research to interviews, surveys and experiments, sources, evidence standards, confidence labels, time plans and agreed outputs. Use whenever someone needs to research something, gets a vague research request, plans a study, market or competitor research, wants to scope how deep to go or needs a research plan before starting.
afeezadebayo/research-learning-skills
Turn research into insight: organising and coding observations, affinity mapping, insight statements, counting and weighing evidence, tensions and surprises, frameworks such as journeys and jobs, implications and prioritised recommendations, and presentations that answer the research question first. Use whenever someone needs to synthesise interviews, surveys, desk research or literature, find themes in research notes, write insights, run affinity mapping or turn findings into recommendations.
afeezadebayo/research-learning-skills
Evaluate sources before relying on them: lateral reading and the SIFT method, deeper checks of authority, method, evidence, currency, purpose and transparency, red flags for statistics, surveys, studies, reports, news, websites, social media and AI outputs, and confidence labels with reasons. Use whenever someone needs to check whether a source is credible, evaluate a statistic, study or report, verify AI-cited sources, judge a website or decide how much to trust information before using it.
afeezadebayo/research-learning-skills
Remember what you learn with retrieval practice and spaced repetition: choosing what is worth remembering, understanding before memorising, one-fact flashcards and cloze deletions, Anki or Leitner systems, daily review routines, practice questions, card maintenance and application at work. Use whenever someone wants to remember what they learn, make flashcards, use Anki, prepare for an exam or certification, learn vocabulary or technical facts, or stop forgetting material.
afeezadebayo/research-learning-skills
Design surveys that produce trustworthy data: objectives tied to decisions, population and sample size with margins of error, neutral single-idea questions, answer formats and scales, ordering and skip logic, pilots, invitations and reminders, cleaning, segment analysis and reports with limitations. Use whenever someone needs to create a survey or questionnaire, run customer or employee feedback surveys, prioritise features with survey data, calculate sample size or fix leading survey questions.
afeezadebayo/research-learning-skills
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Robertjam954/multimodal_rag_application
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Robertjam954/multimodal_rag_application
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
DangQuangSE/team-development-skills
Synchronize docs/ with codebase: update stale docs, discover undocumented features, rebuild CLAUDE.md index. Use after implementation work or periodically.
shimamooo/ENPIRE-so101
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Jarvvski/jjfx
Drafts one GitHub issue or Jira ticket from an ask, has a cheap reviewer challenge its gaps, proposes size or story points and priority, and only after the user approves posts it and verifies what landed. Use when the user says "create an issue", "create a ticket", "draft a Jira story for this", "write this up as a GitHub issue", or asks for a dry run of a ticket. Not for triaging a bug report against existing tickets, turning a spec into a backlog, or pulling tasks out of meeting notes.
by-carlos/plan-staged-rollout