← all publishers

osmontero

@osmontero source repo

Report this profile Claim this profile

• 34 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   Brainstorming · osmontero bundle

   Use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
   0
   installs
2. ▌
   Writing Plans · osmontero bundle

   Use when you have a spec or requirements for a multi-step task, before touching code
   0
   installs
3. ▌
   Processing PDF · osmontero bundle

   Use when the user needs to extract data from PDFs, work with scanned documents, or manipulate PDF files. Triggers include: "extract text from PDF", "convert PDF to text/CSV/images", "scan/OCR this document", "merge/split/rotate PDF", "fill PDF form", "PDF is blank/empty" (likely scanned), or any mention of .pdf files requiring data extraction or transformation. Also use for invoices, receipts, forms, contracts, reports, or any document where structured data (text, tables, form fields) needs to be extracted.
   0
   installs
4. ▌
   Testing Skills · osmontero bundle

   Use when creating or editing a skill that enforces discipline, before deploying it, and when an existing skill is being ignored, argued with, or followed only when convenient. Triggers include writing a new skill, changing a skill's rules, discovering an agent found a loophole in guidance, and needing to know whether a skill actually changes behavior rather than just reading well.
   0
   installs
5. ▌
   Applying Themes · osmontero bundle

   Use when a visual artifact needs a consistent color and type system applied — slide decks, reports, HTML pages, dashboards, PDFs, docs — or when asked to "theme this", "restyle with a palette", "make these slides look consistent", "pick colors and fonts", or to build a custom theme from a brand or a description. Provides 10 contrast-verified themes with semantic tokens and a checker script.
   0
   installs
6. ▌
   Creating Skills · osmontero bundle

   Use when creating new opencode skills, modifying existing skills, or measuring skill performance. Triggers include requests to create a skill from scratch, edit or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
   0
   installs
7. ▌
   Executing Plans · osmontero bundle

   Use when you have a written implementation plan to execute in the current session with review checkpoints, and subagents are unavailable or the tasks are too coupled to delegate
   0
   installs
8. ▌
   Testing Webapps · osmontero bundle

   Use when testing local web applications using Playwright. Triggers include requests to verify frontend functionality, debug UI behavior, capture browser screenshots, view browser logs, or test any web application interactively. Write native Python Playwright scripts for all web application testing tasks.
   0
   installs
9. ▌
   Coauthoring Docs · osmontero bundle

   Use when co-authoring documentation with users through a structured workflow. Triggers include requests to write documentation, proposals, technical specs, decision docs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.
   0
   installs
10. ▌
    Using Superpowers · osmontero bundle

    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
    0
    installs
11. ▌
    Reviewing Security · osmontero bundle

    Use when reviewing code for security before merging or shipping, and when a change touches untrusted input, authentication, authorization, secrets, SQL, subprocess execution, file paths, outbound requests, deserialization, uploads, or third-party dependencies. Triggers include "security review", "is this safe", "can this be exploited", "audit this for vulnerabilities", and adding any new external interface — an endpoint, a webhook, a plugin, or a tool an LLM can call.
    0
    installs
12. ▌
    Creating Slack Gifs · osmontero bundle

    Use when creating animated GIFs optimized for Slack. Triggers include requests like "make me a GIF of X doing Y for Slack", "create a Slack emoji", "animate this for Slack", or any mention of Slack GIFs or Slack emoji animations. Provides constraints, validation tools, and animation concepts for Slack's specific requirements.
    0
    installs
13. ▌
    Using Git Worktrees · osmontero bundle

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
    0
    installs
14. ▌
    Building MCP Servers · osmontero bundle

    Use when building MCP (Model Context Protocol) servers to enable LLMs to interact with external services through well-designed tools. Triggers include requests to create MCP servers, integrate external APIs or services, or build MCP tools in Python (FastMCP) or Node/TypeScript (MCP SDK).
    0
    installs
15. ▌
    Designing Canvas Art · osmontero bundle

    Use when creating beautiful visual art in .png and .pdf documents using design philosophy. Triggers include requests to create posters, pieces of art, designs, or other static visual pieces. Always create original visual designs — never copy existing artists' work to avoid copyright violations.
    0
    installs
16. ▌
    Systematic Debugging · osmontero bundle

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
    0
    installs
17. ▌
    Receiving Code Review · osmontero bundle

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
    0
    installs
18. ▌
    Writing Release Notes · osmontero

    Use when preparing anything that announces a release to the people who consume it — CHANGELOG entries, GitHub release descriptions, version announcements, upgrade or migration guides, or deprecation notices. Triggers include "write the changelog", "release notes for v2.3", "summarize what changed since the last release", "what do users need to know about this upgrade", and cutting a tag.
    0
    installs
19. ▌
    Building Web Artifacts · osmontero bundle

    Use when building elaborate, multi-component HTML artifacts using modern frontend technologies (React, Tailwind CSS, shadcn/ui). Triggers include requests for complex web artifacts requiring state management, routing, or shadcn/ui components. Not for simple single-file HTML/JSX artifacts — use direct generation for those.
    0
    installs
20. ▌
    Requesting Code Review · osmontero bundle

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements
    0
    installs
21. ▌
    Writing Internal Comms · osmontero bundle

    Use when writing communication aimed at colleagues rather than users or customers — 3P updates (Progress/Plans/Problems), status reports, leadership and exec updates, company newsletters, FAQ answers, project updates, incident reports, launch announcements, or policy and reorganization notes. Triggers include "write an update for leadership", "draft the weekly status", "announce this to the company", "write the incident writeup".
    0
    installs
22. ▌
    Test Driven Development · osmontero bundle

    Use when implementing any feature or bugfix, before writing implementation code
    0
    installs
23. ▌
    Creating Algorithmic Art · osmontero bundle

    Use when creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Triggers include requests for generative art, algorithmic art, flow fields, particle systems, or any art created through code. Always create original algorithmic art — never copy existing artists' work to avoid copyright violations.
    0
    installs
24. ▌
    Designing User Experience · osmontero bundle

    Use when designing how an interface behaves rather than how it looks — user flows, navigation and information architecture, forms and validation, loading/empty/error states, confirmation and undo for destructive actions, button and error message wording, feedback for slow operations, or mobile and touch behavior. Also use when a UI looks finished but breaks on bad input, slow networks, no data, or first use.
    0
    installs
25. ▌
    Evolving Apis And Schemas · osmontero bundle

    Use when changing anything other systems or stored data already depend on — editing a .proto file, writing a database migration, adding or dropping a column, renaming a field, changing a response shape, changing an enum, or altering a queue message format. Triggers include "will this break clients", "is this backward compatible", "buf breaking", "ALTER TABLE", "migration", "deprecate this endpoint", and any change to a published API version.
    0
    installs
26. ▌
    Investigating Performance · osmontero bundle

    Use when something is too slow, uses too much memory or CPU, degrades under load, or times out — and before making any change intended to speed something up. Triggers include "this is slow", "optimize this", "high latency", "p99", "memory leak", "it's fine locally but not in production", "the query takes forever", "reduce bundle size", and any request to make code faster.
    0
    installs
27. ▌
    Dispatching Parallel Agents · osmontero bundle

    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
    0
    installs
28. ▌
    Reviewing Interface Quality · osmontero

    Use when asked to review, critique, audit, or improve an existing user interface — "review this UI", "why does this look generic", "make this more polished", "design feedback", "does this look AI-generated", "audit this page". Also use as the final gate before shipping any frontend work, and when a UI renders correctly but feels unfinished, cheap, or inconsistent without an obvious cause.
    0
    installs
29. ▌
    Subagent Driven Development · osmontero bundle

    Use when executing implementation plans with independent tasks in the current session
    0
    installs
30. ▌
    Verifying Before Completion · osmontero bundle

    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
    0
    installs
31. ▌
    Building Finetuning Datasets · osmontero bundle

    Use when preparing to fine-tune, post-train, distill, or LoRA/QLoRA-tune an LLM, when generating synthetic or instruction training data, building SFT/DPO/preference sets, reasoning traces or tool-call trajectories, when choosing rank/alpha/learning rate, when deciding fine-tuning vs RAG, or when a tuned model regressed — hallucinates, lost general ability, repeats, or ignores its format.
    0
    installs
32. ▌
    Designing Frontend Interfaces · osmontero bundle

    Use when building or restyling any web interface — landing pages, dashboards, marketing sites, web apps, React/Vue components, HTML/CSS layouts, artifacts, posters — or when asked to make a UI look better, more polished, more distinctive, less generic, or less "AI-generated". Also use when a design brief, art direction, visual identity, type scale, or color system is needed before implementation.
    0
    installs
33. ▌
    Building Accessible Interfaces · osmontero

    Use when building or auditing any web UI for accessibility — keyboard navigation, screen readers, focus management, ARIA, color contrast, form labels and error announcements, reduced motion, or touch target size. Triggers include "is this accessible", "WCAG", "a11y", "screen reader", "keyboard navigation", "focus trap", "contrast ratio", "aria-label", or building modals, menus, tabs, comboboxes, toasts, and custom controls that must work without a mouse.
    0
    installs
34. ▌
    Finishing A Development Branch · osmontero bundle

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
    0
    installs