Agent Skill
2/7/2026

swe-developing-applications-common

Common software development workflow patterns shared across all language developer agents

W
wahidyankf
6GitHub Stars
1Views
npx skills add wahidyankf/open-sharia-enterprise

SKILL.md

Nameswe-developing-applications-common
DescriptionCommon software development workflow patterns shared across all language developer agents

πŸŒ™ Open Sharia Enterprise

✨ An enterprise solutions platform for Sharia-compliant business systems.

🌐 Live Sites:

  • OSE Platform (oseplatform.com) - Main platform website (under construction)
  • AyoKoding (ayokoding.com) - Engineering research and learnings from this project, shared publicly as educational content
  • OrganicLever (organiclever.com) - Landing and promotional website (Phase 1, in development)

🚧 Project Status

⚠️ Phase 1 - In Development - APIs and implementations may change significantly. Contributions and pull requests are not being accepted at this time.

Current Phase: Phase 1 (OrganicLever - Productivity Tracker)

Building OrganicLever, a full-stack individual productivity tracker:

Next Phase: Phase 2 (SMB Application) - Small and medium business application building on OrganicLever's foundation.

What to Expect:

  • πŸ”„ Breaking changes without notice
  • πŸ“ Architecture still evolving
  • πŸ§ͺ Experimental implementations

See ROADMAP.md for complete development phases and strategy.

πŸš€ Getting Started

πŸ“‹ Prerequisites

  • Node.js 24.13.1 LTS & npm 11.10.1 (managed via Volta)

πŸ“₯ Installation

npm install

πŸ› οΈ Tech Stack

Guiding Principle: Technologies that keep you free - open formats, portable data, no vendor lock-in.

Phase 0 (Complete):

  • Node.js & npm (via Volta) - Tooling and development infrastructure
  • Hugo (Extended) - Static sites (ose-web)
  • Golang - CLI tools (ayokoding-cli, rhino-cli) and future security infrastructure

Current Phase 1 (OrganicLever):

  • Frontend (landing): Next.js + TypeScript
  • Infrastructure: Kubernetes

See ROADMAP.md for complete tech stack evolution across all phases.

πŸ“‚ Project Structure

This project uses Nx to manage applications and libraries:

open-sharia-enterprise/
β”œβ”€β”€ apps/                  # Deployable applications (Nx monorepo)
β”œβ”€β”€ apps-labs/             # Experimental apps and POCs (NOT in Nx monorepo)
β”‚   └── README.md          # Labs directory documentation
β”œβ”€β”€ libs/                  # Reusable libraries (Nx monorepo, flat structure)
β”œβ”€β”€ docs/                  # Project documentation (Diataxis framework)
β”‚   β”œβ”€β”€ tutorials/         # Learning-oriented guides
β”‚   β”œβ”€β”€ how-to/            # Problem-oriented guides
β”‚   β”œβ”€β”€ reference/         # Technical reference
β”‚   └── explanation/       # Conceptual documentation
β”œβ”€β”€ plans/                 # Project planning documents
β”‚   β”œβ”€β”€ in-progress/       # Active project plans
β”‚   β”œβ”€β”€ backlog/           # Planned projects for future
β”‚   └── done/              # Completed and archived plans
β”œβ”€β”€ nx.json                # Nx workspace configuration
β”œβ”€β”€ tsconfig.base.json     # Base TypeScript configuration
β”œβ”€β”€ package.json           # Project manifest with npm workspaces
└── README.md              # This file

Applications (apps/):

Libraries (libs/): Reusable shared code

Labs (apps-labs/): Standalone experiments and POCs (outside Nx)

Learn More: Monorepo Structure Reference | How to Add New App | How to Add New Library | How to Run Nx Commands

πŸ’» Development

Code Quality: Automated checks run on every commit (Prettier formatting, Commitlint validation, markdown linting).

Common Commands:

npm run build                    # Build all projects
npm run test                     # Run tests
npm run lint                     # Lint code
nx dev [app-name]                # Start development server
nx build [app-name]              # Build specific project
nx affected -t build             # Build only affected projects
nx affected -t test:quick        # Run fast quality gate for affected projects
nx graph                         # Visualize dependencies

See Code Quality and Commit Messages for details.

πŸ“Š CI & Test Coverage

All projects enforce β‰₯90% test coverage as part of test:quick.

Quality gates: pre-commit hooks (formatting, linting), pre-push hooks (typecheck, lint, test:quick for affected projects), and PR Quality Gate.

  • OSE Platform
    • Deploy
  • AyoKoding
    • Deploy
  • OrganicLever
    • Deploy
  • Wahidyankf
    • Deploy
  • rhino-cli

For polyglot demo app CI badges, see the ose-primer repository.

πŸ“š Documentation

Organized using the DiΓ‘taxis framework: Tutorials (learning), How-To (problem-solving), Reference (lookup), Explanation (understanding).

See docs/README.md for details.

πŸ”— Related Repositories

  • ose-primer β€” public, MIT-licensed template repository derived from ose-public. Packages scaffolding (governance, AI agents, skills, conventions, CI harness, polyglot demo apps) into a reusable starting point. ose-public is upstream source of truth; propagation and adoption flows are defined by the ose-primer sync convention. For the upstream/downstream relationship and license difference, see Related Repositories reference.

🎯 Motivation

Our mission is to democratize access to trustworthy, Sharia-compliant enterprise technology for organizations of all sizes, regardless of region or industry.

The Opportunity:

  • Islamic enterprise (finance, commerce, cooperatives) is a multi-trillion dollar global market
  • Existing platforms are proprietary, expensive, and domain-limited
  • Most organizations rely on legacy systems retrofitted for Sharia compliance
  • The gap: open-source, compliance-first solutions with radical transparency

Our Solution:

  • Progressive complexity: individual (Phase 1) β†’ SMB (Phase 2) β†’ enterprise (Phase 3)
  • Each phase funds the next; Phase 1/2 success funds Phase 3's certification budget
  • Sharia-compliance built in from the ground up, not bolted on after

What We Believe:

  • πŸ•Œ Sharia-compliance as a foundation - Built in from the ground up, not bolted on later
  • πŸ”“ Transparency builds trust - Open source code enables community verification of Sharia compliance
  • πŸ€– AI-assisted development - Systematic use of AI tools to enhance productivity and code quality
  • πŸ›‘οΈ Security and governance from day one - Architectural foundations, not afterthoughts
  • πŸ“š Learning in public - Share our research and knowledge through ayokoding.com
  • πŸ—οΈ Long-term foundation over quick wins - Building solid foundations for a life-long project

For complete principles, see repo-governance/principles/.

🀝 Contributing

πŸ”’ Contributions are currently closed while we stabilize the architecture and patterns.

πŸŽ‰ Forking is welcome! Build your own version for your region or use case β€” once the foundation is solid, we'll open contributions to the community.

πŸ“œ License

This repository is licensed under the MIT License. All code, documentation, governance materials, specifications, and AI agent configuration are MIT-licensed β€” free to use, fork, modify, and distribute for any purpose.

See LICENSING-NOTICE.md for full details | LICENSE for the root license text | Licensing Convention for internal rules.

Skills Info
Original Name:swe-developing-applications-commonAuthor:wahidyankf