dev1-start

Scaffold a temporary .llm workspace with a feature slug and context file.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Srajangpt1/dataeye --skill dev1-start-srajangpt1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev1-start
Source: https://github.com/Srajangpt1/dataeye/tree/main/packages/browseros-agent/.claude/skills/dev1-start
Command: npx skills add https://github.com/Srajangpt1/dataeye --skill dev1-start-srajangpt1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly aligns teams on a new feature by providing a repeatable, high-level exploration workflow that clarifies stack, structure, and next steps.

Core Features & Use Cases

  • High-level project mapping: Identify languages, frameworks, and major packages in the repo.
  • Workspace scaffolding: Derive a feature slug, create a temporary workspace, and capture initial context.
  • Design handoff readiness: Produce a concise summary to inform the design or hand-off to the next stage.
  • Use Case: For a new feature, start with a quick survey of the codebase and generate a plan to proceed.

Quick Start

Derive a short snake_case feature name from the user's description and scaffold the initial workspace in .llm/<feature_name>/ with a tmp_context.md that records the request, timestamp, and current working directory.

Frequently Asked Questions about dev1-start

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

FAQPage Schema
How do I start development on a new feature in a monorepo?

To start development on a new feature in a monorepo, you can scaffold a temporary workspace by deriving a snake_case feature slug and creating a `.llm` directory with a `tmp_context.md` file to capture initial requests and timestamps.

What is codebase exploration for early-stage feature design?

Codebase exploration for early-stage design is a high-level mapping process that identifies languages, frameworks, and major packages in a repository to clarify the stack and structure before planning next steps.

Does this workflow support design hand-off for large codebases?

Yes, this workflow supports design hand-off for large codebases by producing a concise summary of high-level findings and next steps, ensuring teams align quickly before moving to the next development stage.

Can I scope a feature without manually mapping the entire stack?

Yes, you can scope a feature without manual mapping by using an automated exploration workflow that surveys the codebase to identify your stack, structure, and major packages, generating a plan to proceed.

What are the limitations of high-level project mapping for monorepos?

High-level project mapping for monorepos focuses strictly on early-stage planning and scoping, limiting its utility for deep implementation tasks while primarily serving to document high-level findings for handoff.