All authors
Claude Skills by SDSLeon
github.com/SDSLeon22 skills1 installs57 views
- Heroui ReactHeroUI v3 React component library (Tailwind CSS v4 + React Aria). Use when building UIs with HeroUI — creating Buttons, Modals, Forms, Cards; installing @heroui/react; configuring dark/light themes with oklch variables; or fetching component docs. Keywords: HeroUI, Hero UI, heroui, @heroui/react, @heroui/styles.Votes: 0GitHub stars: 113
- Interactive TestingRun repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol. Use when asked to smoke test, integration test, interactively test, verify a refactor in the UI, reproduce a renderer crash, click through the app, or check that changes did not regress functionality. Build a diff-derived coverage plan, run the scripted baseline and targeted scenarios, complete every required manual gate, capture screenshots and runtime errors, and report expl...Votes: 0GitHub stars: 113
- Provider Chat SmokeSmoke test real Poracode provider chat threads and ACP sessions end to end. Use when validating Qwen Code, Kimi Code, or another structured/ACP provider; testing chat turn handling, steer, Stop, question or permission tools, live model changes, session resume, ACP handshake/capabilities, or provider-chat regressions.Votes: 0GitHub stars: 113
- Release NotesWrite consistent, hand-written-looking changelog entries for a Poracode release. Use when the user wants to "add release notes", "update the changelog", "write the changelog for vX.Y.Z", "cut a release entry", or has just tagged/shipped a release and wants the in-app + website changelog updated. Audits release metadata, every commit, and the full previous-release diff—including direct-commit releases with sparse PR coverage—then distills the user-facing changes and maintainer highlights into ...Votes: 0GitHub stars: 113
- App ControlsInspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP. Use when the request is about the user's workspace state or app-side actions rather than editing files in the repository.Votes: 0GitHub stars: 113
- Browser ControlOpen, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser. Use for visible page state, navigation, screenshots, console or network evidence, and end-to-end UI testing; do not use it for semantic service operations when a purpose-built connector is available.Votes: 0GitHub stars: 113
- Web App VerificationProve a web change actually works by exercising the flow in Poracode's browser and collecting visual, console, and network evidence.Votes: 0GitHub stars: 113
- Chrome ControlUse the user's real Chrome tabs and signed-in sessions for visible browser workflows. Use when existing authentication, open tabs, cookies, or extensions matter; prefer a purpose-built connector for semantic service operations unless the user explicitly asks for Chrome.Votes: 0GitHub stars: 113
- Signed In ResearchGather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.Votes: 0GitHub stars: 113
- Computer UseInspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools. Use for visual workflows that require real windows; prefer Browser for web pages and a purpose-built connector or API when one can complete the task directly.Votes: 0GitHub stars: 113
- Desktop App TestingWalk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself.Votes: 0GitHub stars: 113
- Ci DebugDiagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.Votes: 0GitHub stars: 113
- GithubInspect repositories, review pull requests, triage issues, and follow CI through the GitHub MCP server.Votes: 0GitHub stars: 113
- Publish ChangesCommit work, push a branch, and open a pull request with an accurate description.Votes: 0GitHub stars: 113
- Review Follow UpWork through pull request review feedback: sort what is actionable, fix it, and reply accurately.Votes: 0GitHub stars: 113
- Meeting PrepAssemble what the user needs before a meeting: the event, the attendees, and the mail thread it came from.Votes: 0GitHub stars: 113
- Outlook CalendarRead an Outlook calendar, find meeting times, and create or move events through the Microsoft 365 MCP server.Votes: 0GitHub stars: 113
- Outlook EmailTriage an Outlook inbox, summarize threads, and draft replies through the Microsoft 365 MCP server.Votes: 0GitHub stars: 113
- Parallel ReviewGet independent reviews of the same work from several agents, then reconcile their findings into one verified verdict.Votes: 0GitHub stars: 113
- Subagent DelegationDelegate independent, bounded work to the best available Poracode agents and consolidate verified results. Use for parallel research, independent reviews, specialist work, or non-overlapping implementation; do not delegate trivial, sequential, tightly coupled, or context-heavy work.Votes: 0GitHub stars: 113
- Terminal InspectionRead what the user's Terminal panel is actually printing and report the evidence.Votes: 0GitHub stars: 113
- Skill Creator PoracodeCreate a new reusable agent skill managed by Poracode. Use when the user asks to create, scaffold, or write a new skill, add a managed skill, or turn repeated instructions into a skill. Takes precedence over any agent-native skill-creation flow.Votes: 0GitHub stars: 113