By teslasoft-de
Pack codebases into AI-friendly XML/Markdown bundles for context loading. Supports auto-discovery, segmented bundles, compression. Use for code review, debugging, architecture understanding.
Professional skills and tools for Claude Code, including UX design, authentication patterns, collaboration workflows, and developer tools.
Add this marketplace to Claude Code:
/plugin marketplace add teslasoft-de/claude-skills-marketplace
Then install individual plugins:
/plugin install ux@teslasoft-skills
/plugin install auth-pattern@teslasoft-skills
/plugin install collab@teslasoft-skills
| Plugin | Description |
|---|---|
| ux | Comprehensive UX design skills: research, information architecture, interaction design, visual design, and strategy |
| Plugin | Description |
|---|---|
| auth-pattern | Enterprise authentication patterns: JWT, RBAC, realm-based authorization |
| e2e | E2E testing workflows with test-first development methodology |
| Plugin | Description |
|---|---|
| collab | Git branch collaboration state management for multi-session work |
| context-budget | Context window management with progressive disclosure |
| skill-design | 10-step Skill Design Loop (SDL) for creating agent skills |
| Plugin | Description |
|---|---|
| repomix | Pack codebases into AI-friendly bundles for context loading |
| idea | JetBrains IDE integration via MCP server |
Each plugin follows the standard Claude Code plugin structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest
├── skills/
│ └── skill-name/
│ ├── SKILL.md # Main skill definition
│ └── references/ # Deep content (progressive disclosure)
└── README.md
Teslasoft - teslasoft.de
This project uses dual licensing:
| Use Case | License | Requirements |
|---|---|---|
| Open Source Projects | MIT License | Include copyright notice |
| Commercial / Closed Source | Commercial License | Visible attribution required |
See LICENSE.md for full details.
Commercial use without a Commercial License is prohibited.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
E2E testing workflow with test-first development rules. Covers new features (test-first), test modifications (progressive testing), and refactoring (iterative testing). Framework-agnostic with Playwright/Cypress/Jest examples.
Obsidian vault operations for the Teslasoft PARA-based knowledge management system. Session bootstrapping, note type patterns, 12 template specifications, frontmatter schemas, and Dataview queries.
Design new agent skills using the 10-step Skill Design Loop (SDL). Includes plugin version management tooling (sync, bump, check, status) for all Claude Code marketplace plugins.
AI assistant layer for the Teslasoft harness. Reads pre-collected state from the Drone sidecar, surfaces alerts, answers ad-hoc queries, and replaces manual data collection in dashboard workflows.
Manage context efficiently in long conversations using progressive disclosure and tiered loading. Use when hitting context limits, working on large codebases, or optimizing token usage across multi-turn interactions.
npx claudepluginhub teslasoft-de/claude-skills-marketplace --plugin repomixSlash commands for quick Repomix operations. Pack local and remote repositories with simple commands like /pack-local and /pack-remote.
Safely package codebases with repomix by automatically detecting and removing hardcoded credentials before packing. Use when packaging code for distribution, creating reference packages, or when the user mentions security concerns about sharing code with repomix
Personal Claude Code + Codex dev stack: security hooks, AI-first code conventions, /security-review, /repo-map, /stack-check, portable statusline. Designed to complement other skills-based plugins, not replace them.
Interactive setup wizard for configuring any repository with Claude Code best practices, based on Boris Cherny's workflow
Generate comprehensive analysis and documentation of entire codebase
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.