jsed

Summarize the jsed architecture and vocabulary from AGENTS.md, architecture.md, and vocabulary.md.

Updated Apr 24, 2025
One-click install
npx skills add https://github.com/danielbush/oneput --skill jsed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jsed
Source: https://github.com/danielbush/oneput/tree/main/.agents/skills/jsed
Command: npx skills add https://github.com/danielbush/oneput --skill jsed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This orientation helps developers quickly understand the jsed codebase, its architecture narrative, and the vocabulary so they can contribute effectively.

Core Features & Use Cases

  • Read and internalize the architecture narrative, vocabulary, and module structure so you can explain how jsed works.
  • Provide a high-level overview suitable for onboarding new contributors and stakeholders.
  • Use the understanding to inform future work and decisions about code organization and module boundaries.

Quick Start

Tell me to summarize the jsed codebase after reviewing its AGENTS.md, architecture.md, and vocabulary.md.

Frequently Asked Questions about jsed

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

FAQPage Schema
How do I understand the jsed codebase architecture for onboarding?

To understand the jsed codebase architecture for onboarding, review the AGENTS.md, architecture.md, and vocabulary.md files to internalize the structural narrative, module boundaries, and UPPER_SNAKE_CASE terms used throughout the project.

What is the best way to explain codebase vocabulary to new developers?

The best way to explain codebase vocabulary to new developers is by summarizing the architecture narrative and specific UPPER_SNAKE_CASE terms defined in the project's documentation, ensuring a shared understanding of module boundaries and code organization.

How does the architecture narrative help with software engineering onboarding?

The architecture narrative helps with software engineering onboarding by providing a concise, high-level overview of how the codebase works, allowing new contributors and stakeholders to quickly orient themselves and start contributing effectively.

Can I update the architecture narrative when modifying module boundaries?

Yes, you can update the architecture narrative when modifying module boundaries, as the orientation process applies to updating the architecture narrative and vocabulary to reflect future work and decisions about code organization.

Do I need to read specific files to get a high-level overview of the codebase?

Yes, you need to read AGENTS.md, architecture.md, and vocabulary.md to get a high-level overview of the codebase, as these files contain the structural reasoning and vocabulary needed to explain how the software works.