Skip to main content
iulspop
GitHub creator profile

iulspop

Repository-level view of 36 collected skills across 6 GitHub repositories.

skills collected
36
repositories
6
updated
Aug 4, 2026
repository explorer

Repositories and representative skills

continuous-mode
software-developers

Continuously steers the codebase toward the VISION.md. Reads the vision, assesses current state, picks the highest-impact next action, builds with TDD, commits, and repeats. Never stops. Use when you want autonomous, vision-driven development.

Feb 20, 2026
accessibility
web-and-digital-interface-designers

Audits components and pages for WCAG accessibility issues and suggests fixes. Use when building new UI, reviewing components for a11y compliance, or fixing reported accessibility bugs.

Feb 20, 2026
better-writer
writers-and-authors

Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.

Feb 20, 2026
brainstorm
software-developers

Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.

Feb 20, 2026
code-review
software-quality-assurance-analysts-and-testers

Reviews code changes for correctness, maintainability, security, and adherence to project conventions. Use when reviewing PRs, auditing recent changes, or getting a second opinion on implementation quality.

Feb 20, 2026
commit
software-developers

Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.

Feb 20, 2026
debug
software-developers

Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.

Feb 20, 2026
documentation
software-developers

Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.

Feb 20, 2026
Showing 8 of 21 collected skills.
better-writer
writers-and-authors

Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.

Feb 10, 2026
brainstorm
software-developers

Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.

Feb 10, 2026
commit
software-developers

Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.

Feb 10, 2026
debug
software-developers

Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.

Feb 10, 2026
documentation
software-developers

Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.

Feb 10, 2026
log
software-developers

Logs completed epics and significant accomplishments in reverse chronological order. Use after completing major features, releases, or architecture changes to maintain a project changelog.

Feb 10, 2026
name
software-developers

Suggests clear, descriptive names for functions and variables following consistent naming conventions. Use when naming new code constructs, renaming for clarity, or reviewing naming in code reviews.

Feb 10, 2026
plan
software-developers

Breaks down feature requests into sequential, implementable tasks with code changes under 50 lines each. Use when planning new features, refactors, or multi-step changes to ensure logical ordering and no broken intermediate states.

Feb 10, 2026
Showing 8 of 11 collected skills.
Showing 6 of 6 repositories
All repositories loaded