Skip to main content
Run any Skill in Manus
with one click
$pwd:
jpcaparas
GitHub creator profile

jpcaparas

Repository-level view of 85 collected skills across 2 GitHub repositories, including approximate occupation coverage.

skills collected
85
repositories
2
occupation fields
4
updated
2026-05-26
repository explorer

Repositories and representative skills

#001
superpowers-laravel
52 skills1330updated 2025-11-29
61% of creator
laravel-code-review-requests
Software Quality Assurance Analysts & Testers

Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

2025-11-29
laravel-debugging-prompts
Software Developers

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

2025-11-29
laravel-effective-context
Software Developers

Provide comprehensive context in prompts—files, errors, Laravel version, dependencies, and monorepo details—for accurate AI responses

2025-11-29
laravel-iterating-on-code
Software Developers

Refine AI-generated code through specific feedback—point out errors, identify gaps, show desired changes, reference style guides

2025-11-29
laravel-laravel-prompting-patterns
Software Developers

Use Laravel-specific vocabulary—Eloquent patterns, Form Requests, API resources, jobs/queues—to get idiomatic framework code

2025-11-29
laravel-prompt-structure
Software Developers

Structure prompts for clarity—separate concerns, prioritize requests, specify acceptance criteria, and break work into testable increments

2025-11-29
laravel-specifying-constraints
Software Developers

Define clear constraints—performance, security, testing, architecture, dependencies—so AI generates code that meets your project standards

2025-11-29
laravel-using-examples-in-prompts
Software Developers

Provide concrete examples—existing code patterns, style samples, input/output pairs—to guide AI toward your project's conventions

2025-11-29
Showing top 8 of 52 collected skills in this repository.
#002
skills
33 skills131updated 2026-05-26
39% of creator
audify
Software Developers

Turn a readable resource into cleaned Gemini TTS audio. Use when the user wants to audify a URL, markdown note, HTML page, DOCX, or raw text into an MP3 while stripping markup, HTML, code fences, and bare URLs before synthesis. Triggers on: '/audify', 'read this aloud', 'turn this page into audio', 'make an mp3 narration', 'text to speech this resource', or when Gemini 3.1 Flash TTS with `GEMINI_API_KEY` is the right path. Do NOT trigger for music generation, live voice chat, or binary/media sources that are not meant to be narrated.

2026-05-26
azure-devops-create-work-item
Project Management Specialists

Draft a local Azure DevOps work item packet from loose context, defaulting to a Scrum Product Backlog Item unless the user specifies Bug, Feature, User Story, Task, Issue, or Epic. When run inside a repo, inspect the codebase and include relevant snippets. Save `work-item.md`, `context.md`, `sources.md`, and `metadata.json`. Do NOT use for live Azure DevOps REST/CLI creation, bulk migration, wiki authoring, or status reporting.

2026-05-26
azure-devops-wiki-markdown
Office Clerks, General

Use when writing, fixing, or reviewing Azure DevOps wiki Markdown, Mermaid diagrams, `_TOC_` and `_TOSP_`, collapsible `<details>` blocks, query-table embeds, `@` mentions, work-item links, KaTeX math, HTML video embeds, code fences, or Azure DevOps surface-specific support differences across Wiki, PR, README, Widget, and Done fields. Triggers on Azure DevOps wiki, markdown guidance, Mermaid sequence/graph/timeline/ER diagrams, proposal decision trees, table-of-subpages, query-table, code fence aliases, line-break bugs, and wiki page formatting. Do NOT use for GitHub-only Markdown, generic Mermaid authoring outside Azure DevOps, or non-Azure documentation platforms.

2026-05-26
better-writing
Writers & AuthorsTechnical Writers

Modern writing system for any prose humans read: docs, essays, explainers, PRs, memos, reports, newsletters, UI copy, and landing pages. Starts with Strunk's durable clarity rules, then routes into revision passes for structure, cadence, voice, genericity cleanup, and style-family calibration across technical, analytical, editorial, reflective, and conversion writing. Triggers on: 'rewrite this', 'make this clearer', 'tighten this', 'this sounds stiff', 'fix the voice', 'improve this memo', 'improve this doc', 'sharpen this essay', 'improve this landing page copy'. Do NOT trigger for code-only work, raw research without prose, or factual verification tasks that do not need writing help.

2026-05-26
client-report-from-commits
Project Management Specialists

Turn git commits and diffs since an exact start date into a copy-pastable, non-technical client report grouped by feature. Use when the user wants a client update, accomplishment summary, weekly progress note, stakeholder recap, or high-level status report based on git history. Trigger on: client report from commits, summarize git diff since a date, weekly update from git log, non-technical accomplishments, stakeholder-ready changelog. Do NOT trigger for technical release notes, code review, or any request where the date is still ambiguous.

2026-05-26
eli12
Software Developers

Surgically explain how a codebase, subsystem, feature flow, or cluster of files works in clear, accessible language. Use when the user asks 'how does this work?', wants a code walkthrough, needs architecture explained simply, or wants a digestible mental model with grounded real-world analogies. Trigger on: 'explain this codebase', 'walk me through the flow', 'how does X work', 'what happens when', 'eli12', 'explain it simply', 'make this architecture easier to understand'. Do NOT use for bug triage, code review, literal children's storytelling, or requests that primarily need code changes instead of explanation.

2026-05-26
google-search-ai-optimization
Market Research Analysts & Marketing Specialists

Google-grounded SEO/GEO web development skill for optimizing sites for Google Search, AI Overviews, AI Mode, and agentic browsing without unsupported hacks. Use when building or fixing websites for Search visibility, generative AI search readiness, technical SEO, crawlability, indexability, snippets, structured data, ecommerce/local details, or browser-agent usability. Triggers on: Google AI search, AI Overviews, AI Mode, GEO, AEO, SEO implementation, crawlable content, snippets, llms.txt myths, structured data, Merchant Center, Business Profile, agent-friendly website. Do NOT use for paid ads, generic rank tracking, non-Google LLM directory tactics, or off-page link schemes.

2026-05-26
heuristic-to-deterministic
Software Developers

Convert repeated heuristics, session discoveries, manual review habits, prompt guidance, and flaky one-off fixes into deterministic behavior: validators, normalizers, generators, fixtures, manifests, CI jobs, and hook-ready checks. Use when asked to codify learnings, make behavior reproducible, prevent future agents from guessing, harden a pipeline, convert prompt advice into scripts, or stabilize cross-environment workflows. Triggers on: heuristic to deterministic, codify what we learned, make this deterministic, stop agents second-guessing, turn guidelines into checks, deterministic validator. Do NOT use for pure brainstorming, one-off edits with no repeatable failure mode, subjective taste decisions without measurable signals, or live research where the underlying spec must first be discovered.

2026-05-26
Showing top 8 of 33 collected skills in this repository.
Showing 2 of 2 repositories
All repositories loaded