Kursplattform Development Guidelines

Enforce Kursplattform development guidelines for translations, UI components, themes, and admin templates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Felixzink96/Kursplattform --skill kursplattform-development-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Kursplattform Development Guidelines
Source: https://github.com/Felixzink96/Kursplattform/tree/main/.claude/skills/kursplattform-dev-guidelines
Command: npx skills add https://github.com/Felixzink96/Kursplattform --skill kursplattform-development-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures developers adhere to the Kursplattform project's established coding patterns and best practices, leading to more maintainable and consistent code.

Core Features & Use Cases

  • Enforces Translation Usage: Prevents hardcoded text by mandating the use of the i18n translation system.
  • Standardizes UI Components: Ensures the use of custom, project-specific UI elements for consistency and accessibility.
  • Promotes Theme Adherence: Guarantees that the application's visual theme is consistently applied.
  • Streamlines Admin Page Creation: Mandates the use of AdminPageTemplate for a uniform admin interface.
  • Quick Start: Use the Kursplattform Development Guidelines skill to ensure your new component uses the custom SelectPicker instead of a native <select> element.

Frequently Asked Questions about Kursplattform Development Guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce coding standards in a Next.js project to prevent hardcoded strings?

You enforce coding standards by mandating i18n translation system usage instead of hardcoded strings, ensuring Next.js components route text through established translation patterns for maintainability and consistency.

What is the best way to standardize custom UI components in a TypeScript codebase?

The best way to standardize custom UI components in a TypeScript codebase is to enforce project-specific UI elements like SelectPicker over native HTML elements, ensuring visual consistency and accessibility across the application.

How do I ensure consistent theme system integration across Next.js UI components?

You ensure consistent theme system integration by enforcing project-specific development guidelines that guarantee the application's visual theme is uniformly applied across all custom UI components during the build process.

Does this development guidelines Skill require any specific dependencies for admin page creation?

This development guidelines Skill requires no external dependencies for admin page creation, but mandates using the project-specific AdminPageTemplate to maintain a uniform admin interface and enforce structural consistency.

When should I use the AdminPageTemplate instead of building custom Next.js admin layouts?

You should use the AdminPageTemplate instead of custom Next.js admin layouts whenever you create administrative interfaces, as the Skill enforces this pattern to guarantee a uniform admin experience and maintain structural consistency.

Why does my code review fail when using native HTML select elements instead of custom UI components?

Your code review fails because development guidelines mandate using custom UI components like SelectPicker instead of native HTML select elements to ensure project-wide visual consistency, accessibility, and theme adherence.