walkeros-understanding-development

Guide walkerOS contributors through npm-based build, test, and lint workflows.

342|21|Updated Mar 14, 2022
One-click install
npx skills add https://github.com/elbwalker/walkerOS --skill walkeros-understanding-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walkeros-understanding-development
Source: https://github.com/elbwalker/walkerOS/tree/main/skills/walkeros-understanding-development
Command: npx skills add https://github.com/elbwalker/walkerOS --skill walkeros-understanding-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers contributing to walkerOS by codifying project conventions, build/test/lint workflows, and XP principles.

Core Features & Use Cases

  • Guided onboarding: Clear rules for build/test/lint workflow, XP principles, and folder structure.
  • Quality-focused development: Encourages TDD, DRY, KISS, and no use of any in production code.
  • Use Case: A new contributor uses this skill to align their PR with project conventions before coding.

Quick Start

Run npm install to install dependencies, then use npm run dev to start watchers, npm run build to compile, npm run test to verify tests, and npm run lint to check code quality.

Frequently Asked Questions about walkeros-understanding-development

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

FAQPage Schema
What development workflow conventions should I follow for walkerOS contributions?

walkerOS development workflow requires using npm-based tooling for install, build, test, lint, and format, while adhering to XP principles like TDD, DRY, and KISS across all package contributions.

How do I start a new feature in walkerOS using TDD and XP principles?

To start a feature in walkerOS, run `npm install` for dependencies, then use `npm run dev` for watchers and `npm run test` to verify, ensuring Test-Driven Development (TDD) guides your implementation.

Does walkerOS allow using `any` type in production code?

No, walkerOS explicitly forbids the use of `any` in production code to maintain quality. The project enforces DRY and KISS principles alongside strict type checking via `npm run lint`.

What npm scripts are required to verify walkerOS code quality before submitting a PR?

To verify walkerOS code quality before a PR, run `npm run build` to compile, `npm run test` to execute tests, `npm run lint` to check quality, and `npm run format` to standardize styling.