GitHub
convert-beehiiv-newsletter
Converts Beehiiv newsletter posts into properly formatted blog markdown files. Use when converting newsletters to blog posts, importing Beehiiv content, or creating blog posts from newsletter URLs.
Skills IA Entreprise
Découvrez les skills Entreprise, comparez leurs dépôts et consultez leurs instructions.
Catégories: Entreprise
Entreprise Effacer les filtres
Explorer
GitHub
ag-ui-protocol
AG-UI (Agent-User Interaction) protocol reference for building AI agent frontends. Use when implementing AG-UI events (RUN_STARTED, TEXT_MESSAGE_*, TOOL_CALL_*, STATE_*), building agents that communicate with f...
GitHub
ai-sdk
Vercel AI SDK reference for building AI-powered applications. Use when implementing text/object generation (generateText, streamText, generateObject, streamObject), building chatbots with useChat/useCompletion...
GitHub
brane-ship
Complete workflow for verifying and committing Brane SDK changes. Run after implementing fixes/features to verify impact, test affected modules, and prepare for commit.
GitHub
brane-debugging
Systematic approach to debugging Brane SDK issues. Use when diagnosing transaction failures, RPC errors, encoding mismatches, or unexpected behavior.
GitHub
brane-impact
Analyze change impact and discover affected tests. Use after making changes to understand what depends on the modified code, find relevant tests, and determine what to run.
GitHub
brane-docs
Update Javadoc and public documentation after implementing features. Use when finishing implementation to ensure both internal (Javadoc) and external (website docs) documentation are accurate and complete.
GitHub
brane-code-review
Review Brane SDK code for correctness, Java 21 patterns, type safety, and architectural consistency. Use when reviewing PRs, checking code changes, or validating implementations against Brane standards.
GitHub
brane-research
Research EVM SDK patterns from viem (TypeScript) and alloy (Rust) when designing Brane features. Use when implementing new functionality, designing APIs, or solving problems that other SDKs have already address...
GitHub
mermaid-diagrams
Has guidelines for creating Mermaid diagrams and fixing its syntax errors. Use this before creating or updating Mermaid diagrams.
GitHub
plan-with-tdd-and-prd
Use when initiating new features, complex code changes, or technical research tasks that require structured planning and documentation before implementation.
GitHub
review-with-subagent
Instructions for reviewing changes using subagents. Use after implementation and verification are complete
GitHub
high-density-writing-style
Guidelines for a writing style that's concise and direct. aka High density language, HD style Use for writing/editing prompts, artefact documents, TDD, PRD, discovery documents, research, AGENTS.md, and more.
GitHub
plan-mode
Guidelines for Plan Mode - focus on planning before implementation
GitHub
explain-code
Gives guidelines on how to explain code with call graphs and pseudocode. Invoke this when creating code explanations. Common user requests: - "Explain {feature or function}" - "Show me how {feature} works" - "C...
GitHub
solution-options-document
Write solution options documents to evaluate and compare different technical approaches with trade-off analysis Common user requests: - "Evaluate options for [problem]" - "Compare [solution A] vs [solution B]"...
GitHub
refine-implementation
Refine an implementation
GitHub
triangulate-plan
Get alternative perspectives on a plan
GitHub
verify-implementation
Guidelines for automated and manual verification of code changes. When to use: - After making code changes to ensure correctness As part of the implementation workflow
GitHub
execute-plan
Use when executing implementation plans from planning phase to verified completion
GitHub
ralph-loop
tbd
GitHub
analyse-and-review-pr
Analyse and review a pull request
GitHub
reflect
Distill learnings into improvements for the skills and AGENTS.md instructions
GitHub
generate-changelog
Guidelines for documenting work in a changelog artefact after implementing and verifying work
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.