Marius Jørgensen
Community@marjorg · Oslo
Marius Jørgensen maintains a 52-skill registry covering disciplined software engineering: TDD, debugging, code review, CI/CD, security hardening, and spec-driven delivery.
Agent Skills by Marius Jørgensen
Showing 52 vetted skills indexed across 1 GitHub repositories.
idea-refine
Refines raw ideas into actionable one-pagers through structured divergent and convergent thinking.
comments
Guides writing minimal, high-value code comments and TODOs during code editing.
debugging-and-error-recovery
Diagnose test failures, build errors, and runtime bugs through structured root-cause triage.
using-agent-skills
Discovers and routes tasks to the appropriate engineering workflow skill.
test-driven-development
Guides implementation of code changes using the red-green-refactor test-driven development cycle.
planning-and-task-breakdown
Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.
incremental-implementation
Implements multi-file code changes in thin, tested, individually committed vertical slices.
api-and-interface-design
Guides design of stable REST APIs, TypeScript interfaces, and module contracts.
ci-cd-and-automation
Configures CI/CD pipelines with quality gates, deployment strategies, and GitHub Actions workflows.
context-engineering
Configures rules files, specs, and context budgets to improve AI agent output quality.
frontend-ui-engineering
Builds accessible, responsive React components following design system and WCAG standards.
shipping-and-launch
Guides production deployments with pre-launch checklists, staged rollouts, monitoring, and rollback plans.
spec-driven-development
Creates structured specifications through a gated specify-plan-tasks-implement workflow before coding.
constraint-driven-development
Establishes enforceable project quality constraints in a CONSTRAINTS.md file with thresholds and diff-scoped guards.
code-review-and-quality
Reviews code changes across correctness, readability, architecture, security, and performance before merge.
skill-creator
Create, evaluate, and iteratively improve Claude skills with benchmarks and description optimization.
security-and-hardening
Hardens web application code against OWASP Top 10 vulnerabilities and supply-chain risks.
deprecation-and-migration
Plans deprecation and incremental migration of legacy systems, APIs, and database schemas.
observability-and-instrumentation
Instruments production code with structured logs, metrics, traces, and symptom-based alerts.
interview-me
Extracts underlying user intent through one-question-at-a-time interviews before planning or coding.
code-simplification
Refactors working code to reduce complexity while preserving exact behavior.
doubt-driven-development
Subjects non-trivial decisions to fresh-context adversarial review before they stand.
source-driven-development
Verifies framework code patterns against official documentation and cites sources.
performance-optimization
Diagnose and fix frontend, backend, and database performance bottlenecks through measurement-driven workflows.
Frequently Asked Questions About Marius Jørgensen
FAQPage SchemaWhat tasks can I accomplish with Marius Jørgensen's skill registry?▼
The 52 skills cover the full delivery cycle: refining ideas, writing specs and PRDs, breaking work into tickets, test-driven implementation, multi-axis code review, debugging, security hardening, performance optimization, CI/CD setup, observability instrumentation, and production launch checklists with rollback strategies.
Who is the target audience for these engineering skills?▼
Software engineers and engineering leads who want disciplined, verifiable development practices. The skills suit developers handling ambiguous requirements, high-stakes changes like auth or migrations, accessibility and WCAG compliance work, and teams needing documented standards, ADRs, and enforced quality constraints.
How do I install and start using these skills?▼
Run the setup-matt-pocock-skills skill once to configure the repo's issue tracker, triage labels, and domain doc layout. After that, the using-agent-skills meta-skill or the ask-matt router discovers and invokes the right skill for each piece of work automatically.
What prerequisites or dependencies do these skills require?▼
Most skills run standalone, but browser-testing-with-devtools requires the chrome-devtools MCP server to be configured. Ticket-publishing skills like to-tickets and to-spec work with local files or a configured issue tracker, and constraint-driven-development writes a CONSTRAINTS.md file into the project.
Do these skills enforce code quality automatically?▼
Yes. The constraint-driven-development skill records quality thresholds in CONSTRAINTS.md and watches diffs for weakened standards such as new @ts-ignore suppressions, skipped tests, or lowered coverage. Code-review skills check changes against documented standards and the originating spec in parallel.