Claude Skills by ulises-jeremias

'WHAT - Interactive project assessment router: define assessment scope and units, collect

WHAT - Produce spike and research findings using the spike template; captures purpose, findings,

WHAT - Draft and review technical tasks using the Best Practices Task Template; includes

WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend,

WHAT — Draft and review a Technical Requirements Document (TRD) using the template, typically

WHAT - Draft and review user stories using the task template plus the As a/I want/so that

WHAT - Router for creating and refining epics, user stories, tasks, bugs, and incidents using

WHAT — Interactive interview to capture client delivery context and store it inside the user's

'WHAT — Generic client delivery: Jira or ClickUp, full repo context, human gates, English

WHAT - Evidence-based design-unit assessment orchestrated by project-assessment. Evaluates visual hierarchy, UX friction, interaction, a11y, responsiveness, design-system compliance, and distinctiveness with severity/confidence evidence citations. Reuses project-assessment-evidence semantics — no second framework.

WHAT - Browser-grounded iterative design improvement. Consumes design-assessment findings, defines direction, prioritizes safe vs ambiguous changes, implements within existing design system, runs app, captures rendered evidence via browser, reviews and iterates. Reuses evidence model — no new scoring framework.

Connects Figma design components to code components using Code Connect mapping tools. Use

Generates custom design system rules for the user's codebase. Use when user says "create

Create a new blank Figma file. Use when the user wants to create a new Figma design or FigJam

Translates Figma designs into production-ready application code with 1:1 visual fidelity.

Use the Figma MCP server to fetch design context, screenshots, variables, and assets, and

'Review and create distinctive, production-grade frontend interfaces with high design quality

Guidance for distinctive, intentional visual design when building new UI or reshaping an

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI",

Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

Triage and address open GitHub PR review and conversation comments using the gh CLI. Use

Daily GitHub contribution planner — analyzes the gh-logged-in user's non-archived repos (owned

Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose

'HOW — GitHub CLI (gh): push branch, create draft PR with title/body from template or file;

'HOW — GitLab CLI (glab): push branch, create draft MR with title/body; fallback untracked

Manage Git worktrees per writer for Agent Toolkit swarms — isolated branches, handoff promotion,

ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user

Confluence administration including users, groups, space settings, and permission diagnostics. Use when managing user access, group membership, viewing space configuration, or checking permissions.

View analytics, statistics, and popularity metrics for Confluence content. ALWAYS use when user wants to see views, popularity, or contributor stats.

Central hub for Confluence operations - routes requests to specialized skills. ALWAYS use when user mentions confluence, wiki, or Atlassian wiki operations.

Manage file attachments - upload, download, list, and delete attachments. ALWAYS use when user wants to work with files on pages.

Bulk operations for 50+ pages - updates, moves, deletions, labels, and permissions. Use when updating multiple pages simultaneously (dry-run preview included), needing rollback safety, or coordinating team changes. Handles partial failures gracefully.

Manage comments on Confluence pages - add, get, update, delete, and resolve comments. ALWAYS use for feedback, discussions, and inline annotations.

Navigate and manage Confluence page hierarchies, ancestors, descendants, and trees. ALWAYS use for parent/child relationships and page tree navigation.

JIRA integration - embed issues, create links between products. ALWAYS use when user wants to connect Confluence and JIRA.

Manage content labels - add, remove, and search by labels. ALWAYS use when user wants to tag, label, or categorize content.

Cache management, API diagnostics, and operational utilities. Use when optimizing performance, managing cache, diagnosing API issues, or troubleshooting Confluence connectivity.

Manage Confluence pages and blog posts - create, read, update, delete, copy, move, and version control. ALWAYS use when user wants to work with page content, create pages, update pages, or manage page versions.

Manage space and page permissions and restrictions. ALWAYS use when user wants to control access, set restrictions, or manage who can view/edit content.

Manage content properties (custom metadata) on Confluence pages and blog posts. ALWAYS use for custom metadata, key-value data, or application-specific fields.

Search Confluence using CQL queries, validate syntax, export results, and manage search history. ALWAYS use when user wants to find, search, or query for content.

Manage Confluence spaces - create, list, update, delete, and configure spaces. ALWAYS use when user wants to work with spaces (not individual pages).

Work with page templates and blueprints. ALWAYS use when user wants to create standardized pages or manage templates.

Content watching and notifications. ALWAYS use when user wants to follow content or manage notifications.

Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.

Epic creation and sprint management - create epics, manage sprints, view backlog, estimate with story points. TRIGGERS: 'create an epic', 'create epic', 'new epic', 'show the backlog', 'view backlog', 'add to sprint', 'move to sprint', 'set story points', 'sprint planning', 'epic for', 'link to epic', 'sprint list', 'active sprint', 'velocity', 'create subtask'. NOT FOR: bugs/tasks/stories without epic context (use jira-issue), field ID discovery (use jira-fields), searching issues by JQL (us...

JIRA automation hub routing to 13 specialized skills for any JIRA task: issues, workflows, agile, search, time tracking, service management, and more.

Bulk operations for multiple issues at scale. TRIGGERS: 'bulk update', 'bulk close', 'bulk transition', 'bulk assign', 'transition N issues' (N >= 10), 'update all bugs', 'close 50 issues', 'mass transition', 'update multiple issues', quantities like '50 issues', '100 bugs', '20+ tickets'. Use for operations on 10+ issues. NOT FOR: single issue transitions (use jira-lifecycle), searching only without modifications (use jira-search), single issue field updates (use jira-issue).

Collaborate on issues: add/edit comments, share attachments, notify users, track activity. For team communication and coordination on JIRA issues.

Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield_', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA field metadata and discovery. NOT FOR: setting field values on issues (use jira-issue), setting story points (use jira-agile), searching by field values (use jira-search).