keepsimpleoss

Enforce KeepSimpleOSS development guidelines for component structure, styling, and conventions.

7|Updated Dec 10, 2025

Search Tags:#typescript #design-system #component-patterns #pages-router #import-order #keepsimple #scss-modules

Ready to run

npx skills add https://github.com/keepsimpleio/KeepSimpleOSS --skill keepsimpleoss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keepsimpleoss
Source: https://github.com/keepsimpleio/KeepSimpleOSS/tree/main/.claude/skills/keepsimple
Command: npx skills add https://github.com/keepsimpleio/KeepSimpleOSS --skill keepsimpleoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes KeepSimpleOSS development to prevent drift in component structure, styling, and conventions.

Core Features & Use Cases

Enforces directory structure, file naming, and exports for components.
Defines styling rules (SCSS modules only), design system guidance, and import order.
Guides routing, data organization, i18n patterns, and utilities placement to maintain consistency.

Quick Start

Review AGENTS.md and adhere to the KeepSimple style rules when creating or updating components.

Frequently Asked Questions about keepsimpleoss

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

FAQPage Schema

How do I enforce consistent component patterns and import order in a TypeScript project?▼

You can standardize TypeScript component patterns by applying rules for directory structures, SCSS modules, and import order. This enforces design system compliance and prevents pattern drift across the repository's components.

How do I standardize SCSS module usage and file naming conventions in my repository?▼

Standardize SCSS module usage and file naming by enforcing specific directory structures and styling rules. The Skill checks component exports and guides data organization to maintain strict consistency across the codebase.

What is the best way to prevent component structure drift when scaling a design system?▼

Preventing component structure drift when scaling a design system requires enforcing strict guidelines for component creation, routing, and naming conventions. This ensures standardized development and maintains structural integrity across the project.

Does this Skill work with Next.js pages router and i18n data organization?▼

Yes, it works with Next.js pages router and i18n patterns by providing specific guidance for routing, data organization, and utilities placement to maintain consistency across these architectural elements.

Why should I use standardized coding rules for component creation and styling?▼

Using standardized coding rules for component creation and styling prevents pattern drift and maintains repository consistency. It enforces design system guidance, SCSS usage, and import order to streamline development.