swe-developing-applications-common

Standardize cross-language development workflows for OSE-style Nx monorepos.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill swe-developing-applications-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-developing-applications-common
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/swe-developing-applications-common
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill swe-developing-applications-common

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent development practices across different programming languages in OSE-style Nx monorepos, ensuring all developer agents follow the same standardized processes for tooling, version control, testing, and code quality.

Core Features & Use Cases

  • Universal Nx Monorepo Guidance: Standardized commands for development, building, testing, and affected project analysis, plus best practices for app/library separation, dependency management, and avoiding circular dependencies.
  • Standardized Git & Commit Workflow: Trunk-based development rules, conventional commit formatting requirements, and pre-commit automation (Husky, lint-staged, commitlint) configuration to enforce code quality.
  • TDD & Environment Standards: Mandatory Red→Green→Refactor cycle for all code changes, plus step-by-step environment setup using npm run doctor and rhino-cli for toolchain convergence and environment file management.
  • Use Case: A developer working on both a Go backend microservice and a Next.js frontend can follow the exact same workflow, commit standards, and testing practices without learning separate language-specific processes.

Quick Start

Use this skill to follow the standardized 6-step development workflow when building a new feature in any OSE monorepo project, including writing failing tests first, using canonical Nx commands, and adhering to conventional commit formatting.

Frequently Asked Questions about swe-developing-applications-common

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

FAQPage Schema
How do I standardize development workflows across multiple languages in an Nx monorepo?

To standardize Nx monorepo workflows across multiple languages, apply universal guidance for canonical Nx commands, trunk-based git practices, and TDD standards to ensure all developer agents follow consistent processes.

How does conventional commit formatting work with pre-commit automation in a polyglot monorepo?

Conventional commit formatting in a polyglot monorepo works by enforcing trunk-based development rules through pre-commit automation tools like Husky, lint-staged, and commitlint to guarantee code quality before integration.

What is the standard TDD cycle for building features in an OSE-style monorepo?

The standard TDD cycle for building features in an OSE-style monorepo is the mandatory Red→Green→Refactor sequence, requiring failing tests first before progressing through the standardized 6-step development workflow.

Do I need npm run doctor and rhino-cli to set up my Nx monorepo development environment?

Yes, you need npm run doctor and rhino-cli for environment setup to achieve toolchain convergence and manage environment files, ensuring your local setup aligns with OSE monorepo standards.

Can I use the same git workflow and testing practices for Go backend and Next.js frontend projects?

Yes, developers working on Go backend and Next.js frontend projects can follow the exact same git workflow, conventional commit standards, and TDD practices without learning separate language-specific processes.

How do I avoid circular dependencies when separating apps and libraries in an Nx workspace?

To avoid circular dependencies in an Nx workspace, follow best practices for app and library separation, utilize affected project analysis, and apply standardized dependency management rules across the monorepo structure.