yjcli 0.0.1__py3-none-any.whl

yjcli/__init__.py

@@ -0,0 +1,3 @@
+"""yjcli — platform/service scaffold and agent wiring."""
+
+__version__ = "0.0.1"

yjcli/__main__.py

@@ -0,0 +1,4 @@
+from yjcli.cli import app
+
+if __name__ == "__main__":
+    app()

yjcli/cli.py

@@ -0,0 +1,51 @@
+"""Entry: register subcommands (Typer)."""
+
+from __future__ import annotations
+
+from typing import Optional
+
+import typer
+
+from yjcli import __version__
+from yjcli.commands import add
+from yjcli.commands.init_cmd import init_cmd
+from yjcli.services import status
+
+app = typer.Typer(
+    name="yjcli",
+    help="Scaffold YJ platforms/services and Cursor/Claude agent wiring.",
+    no_args_is_help=True,
+)
+
+
+def _version_callback(value: bool) -> None:
+    if value:
+        typer.echo(__version__)
+        raise typer.Exit()
+
+
+@app.callback()
+def main(
+    version: Optional[bool] = typer.Option(
+        None,
+        "--version",
+        "-V",
+        help="Print version and exit.",
+        callback=_version_callback,
+        is_eager=True,
+    ),
+) -> None:
+    """yjcli root options."""
+
+
+app.command("init")(init_cmd)
+app.add_typer(add.app, name="add")
+
+
+@app.command("doctor")
+def doctor() -> None:
+    """Show packaged template/skill/rule counts."""
+    assets = status.asset_summary()
+    typer.echo("yjcli packaged data:")
+    for key, n in assets.items():
+        typer.echo(f"  {key}: {n} files")

yjcli/commands/__init__.py

@@ -0,0 +1 @@
+"""CLI command groups (thin entry handlers)."""

yjcli/commands/add.py

@@ -0,0 +1,95 @@
+"""yjcli add <resource> — extend an existing repo."""
+
+from __future__ import annotations
+
+from pathlib import Path
+from typing import Optional
+
+import typer
+
+from yjcli.modules.constants import PLATFORMS
+from yjcli.services import scaffold
+
+app = typer.Typer(help="Add a platform or service to the current repo.")
+
+
+@app.command("platform")
+def add_platform(
+    platform: Optional[list[str]] = typer.Option(
+        None,
+        "--platform",
+        "-p",
+        help="Platform to add (repeatable). Interactive if omitted.",
+    ),
+    all_platforms: bool = typer.Option(
+        False,
+        "--all",
+        help="Add all missing platforms.",
+    ),
+    force: bool = typer.Option(
+        False,
+        "--force",
+        "-f",
+        help="Overwrite existing root/agent files without prompting.",
+    ),
+    path: Path = typer.Option(
+        Path("."),
+        "--path",
+        help="Target repository root (default: cwd).",
+        file_okay=False,
+        dir_okay=True,
+        resolve_path=True,
+    ),
+) -> None:
+    """Add one or more platform roots from packaged templates."""
+    if all_platforms and platform:
+        typer.echo("error: use either --all or --platform, not both", err=True)
+        raise typer.Exit(code=1)
+    if platform:
+        unknown = [p for p in platform if p not in PLATFORMS]
+        if unknown:
+            typer.echo(
+                f"error: unknown platform(s): {', '.join(unknown)}",
+                err=True,
+            )
+            raise typer.Exit(code=1)
+
+    scaffold.bootstrap(
+        path,
+        platforms=platform,
+        all_platforms=all_platforms,
+        force=force,
+        mode="add",
+    )
+
+
+@app.command("service")
+def add_service(
+    platform: Optional[str] = typer.Option(
+        None,
+        "--platform",
+        "-p",
+        help="Existing platform root. Interactive if omitted.",
+    ),
+    name: Optional[str] = typer.Option(
+        None,
+        "--name",
+        "-n",
+        help="Service/app name. Interactive if omitted.",
+    ),
+    path: Path = typer.Option(
+        Path("."),
+        "--path",
+        help="Target repository root (default: cwd).",
+        file_okay=False,
+        dir_okay=True,
+        resolve_path=True,
+    ),
+) -> None:
+    """Add a service/app under an existing platform."""
+    if platform and platform not in PLATFORMS:
+        typer.echo(f"error: unknown platform: {platform}", err=True)
+        typer.echo(f"known: {', '.join(PLATFORMS)}", err=True)
+        raise typer.Exit(code=1)
+
+    scaffold.add_service_flow(path, platform=platform, name=name)

yjcli/commands/init_cmd.py

@@ -0,0 +1,61 @@
+"""yjcli init — bootstrap the current repo."""
+
+from __future__ import annotations
+
+from pathlib import Path
+from typing import Optional
+
+import typer
+
+from yjcli.modules.constants import PLATFORMS
+from yjcli.services import scaffold
+
+
+def init_cmd(
+    platform: Optional[list[str]] = typer.Option(
+        None,
+        "--platform",
+        "-p",
+        help="Platform to create (repeatable). Interactive if omitted.",
+    ),
+    all_platforms: bool = typer.Option(
+        False,
+        "--all",
+        help="Create all known platforms.",
+    ),
+    force: bool = typer.Option(
+        False,
+        "--force",
+        "-f",
+        help="Overwrite existing root/agent files without prompting.",
+    ),
+    path: Path = typer.Option(
+        Path("."),
+        "--path",
+        help="Target repository root (default: cwd).",
+        file_okay=False,
+        dir_okay=True,
+        resolve_path=True,
+    ),
+) -> None:
+    """Bootstrap root templates, agent wiring, and selected platforms."""
+    if all_platforms and platform:
+        typer.echo("error: use either --all or --platform, not both", err=True)
+        raise typer.Exit(code=1)
+    if platform:
+        unknown = [p for p in platform if p not in PLATFORMS]
+        if unknown:
+            typer.echo(
+                f"error: unknown platform(s): {', '.join(unknown)}",
+                err=True,
+            )
+            typer.echo(f"known: {', '.join(PLATFORMS)}", err=True)
+            raise typer.Exit(code=1)
+
+    scaffold.bootstrap(
+        path,
+        platforms=platform,
+        all_platforms=all_platforms,
+        force=force,
+        mode="init",
+    )

yjcli/data/claude-rules/output-discipline.md

@@ -0,0 +1,11 @@
+---
+description: Output and documentation discipline - concise table-first results; do not touch docs unless asked
+---
+
+# Output & Docs Discipline
+
+- Present results concisely; summarize as a table when possible.
+- Show only the summary. Do not dump raw execution output, full logs, or intermediate artifacts.
+- No filler, no repeated explanations.
+- Switch to detailed output only when the user explicitly asks (e.g. "자세히"): keep the table first, then add reasoning and key code excerpts.
+- Do not create or modify docs (README, etc.) unless the user explicitly asks. When editing a doc, rewrite it in context so it stays in sync with the code.

yjcli/data/claude-rules/skill-backend-msa.md

@@ -0,0 +1,9 @@
+---
+description: Route backend/ edits to yj-backend-msa skill
+paths:
+  - "backend/**"
+---
+
+# Skill routing
+
+Read and follow `yj-backend-msa` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/claude-rules/skill-backend-service.md

@@ -0,0 +1,10 @@
+---
+description: Route backend-service/ and native host edits to yj-backend-service skill
+paths:
+  - "backend-service/**"
+  - "browser-extension/native_*/**"
+---
+
+# Skill routing
+
+Read and follow `yj-backend-service` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/claude-rules/skill-browser-extension.md

@@ -0,0 +1,10 @@
+---
+description: Route browser-extension/ (non-native) edits to yj-browser-extension skill
+paths:
+  - "browser-extension/**"
+---
+
+# Skill routing
+
+Read and follow `yj-browser-extension` (with `yj-arch-core`) for extension UI/background/content.
+If the path is `browser-extension/native_*/**`, use `yj-backend-service` instead.

yjcli/data/claude-rules/skill-cli.md

@@ -0,0 +1,9 @@
+---
+description: Route cli/ edits to yj-cli skill
+paths:
+  - "cli/**"
+---
+
+# Skill routing
+
+Read and follow `yj-cli` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/claude-rules/skill-frontend.md

@@ -0,0 +1,9 @@
+---
+description: Route frontend/ edits to yj-frontend skill
+paths:
+  - "frontend/**"
+---
+
+# Skill routing
+
+Read and follow `yj-frontend` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/claude-rules/skill-mobile-app.md

@@ -0,0 +1,9 @@
+---
+description: Route mobile-app/ edits to yj-mobile-app skill
+paths:
+  - "mobile-app/**"
+---
+
+# Skill routing
+
+Read and follow `yj-mobile-app` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/claude-rules/skill-pc-app.md

@@ -0,0 +1,9 @@
+---
+description: Route pc-app/ edits to yj-pc-app skill
+paths:
+  - "pc-app/**"
+---
+
+# Skill routing
+
+Read and follow `yj-pc-app` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/claude-rules/yj-arch-core.md

@@ -0,0 +1,7 @@
+---
+description: Always load yj-arch-core skill for coding work
+---
+
+# Architecture skill
+
+When creating, modifying, reviewing, or refactoring code, read and follow the project skill `yj-arch-core`, then exactly one matching `yj-*` platform skill for the folder being edited.

yjcli/data/cursor-rules/output-discipline.mdc

@@ -0,0 +1,12 @@
+---
+description: Output and documentation discipline - concise table-first results; do not touch docs unless asked
+alwaysApply: true
+---
+
+# Output & Docs Discipline
+
+- Present results concisely; summarize as a table when possible.
+- Show only the summary. Do not dump raw execution output, full logs, or intermediate artifacts.
+- No filler, no repeated explanations.
+- Switch to detailed output only when the user explicitly asks (e.g. "자세히"): keep the table first, then reasoning and the key code excerpts.
+- Do not create or modify docs (README, etc.) unless the user explicitly asks. When editing a doc, rewrite it in context so it stays in sync with the code.

yjcli/data/cursor-rules/skill-backend-msa.mdc

@@ -0,0 +1,9 @@
+---
+description: Route backend/ edits to yj-backend-msa skill
+globs: backend/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-backend-msa` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/cursor-rules/skill-backend-service.mdc

@@ -0,0 +1,9 @@
+---
+description: Route backend-service/ and native host edits to yj-backend-service skill
+globs: backend-service/**,browser-extension/native_*/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-backend-service` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/cursor-rules/skill-browser-extension.mdc

@@ -0,0 +1,10 @@
+---
+description: Route browser-extension/ (non-native) edits to yj-browser-extension skill
+globs: browser-extension/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-browser-extension` (with `yj-arch-core`) for extension UI/background/content.
+If the path is `browser-extension/native_*/**`, use `yj-backend-service` instead.

yjcli/data/cursor-rules/skill-cli.mdc

@@ -0,0 +1,9 @@
+---
+description: Route cli/ edits to yj-cli skill
+globs: cli/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-cli` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/cursor-rules/skill-frontend.mdc

@@ -0,0 +1,9 @@
+---
+description: Route frontend/ edits to yj-frontend skill
+globs: frontend/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-frontend` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/cursor-rules/skill-mobile-app.mdc

@@ -0,0 +1,9 @@
+---
+description: Route mobile-app/ edits to yj-mobile-app skill
+globs: mobile-app/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-mobile-app` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/cursor-rules/skill-pc-app.mdc

@@ -0,0 +1,9 @@
+---
+description: Route pc-app/ edits to yj-pc-app skill
+globs: pc-app/**
+alwaysApply: false
+---
+
+# Skill routing
+
+Read and follow `yj-pc-app` (with `yj-arch-core`). Do not apply other platform skills.

yjcli/data/cursor-rules/yj-arch-core.mdc

@@ -0,0 +1,8 @@
+---
+description: Always load yj-arch-core skill for coding work
+alwaysApply: true
+---
+
+# Architecture skill
+
+When creating, modifying, reviewing, or refactoring code, read and follow the project skill `yj-arch-core`, then exactly one matching `yj-*` platform skill for the folder being edited.

yjcli/data/skills/yj-arch-core/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: yj-arch-core
+description: >-
+  Repository architecture constitution for this monorepo. Use on every coding,
+  review, or refactor task. Enforces fixed platform roots, unified env file
+  names, universal entry/flow/domain/view/infra roles, acyclic imports, and
+  minimal edit scope. Always apply together with exactly one matching yj-*
+  platform skill for the folder being edited.
+---
+
+# yj-arch-core
+
+## Purpose
+
+Reduce AI cost and blast radius. Do not reinterpret the whole repo, add
+wrappers/layers, or read unrelated platforms.
+
+1. Existing repo conventions win when clearer than this skill.
+2. Identify the platform root folder first, then load **only** that platform skill.
+3. Edit the smallest file set that owns the change.
+
+## Fixed platform roots
+
+```text
+backend/              # MSA + gRPC (yj-backend-msa)
+backend-service/      # single BE (yj-backend-service)
+frontend/             # yj-frontend
+mobile-app/           # yj-mobile-app
+pc-app/               # yj-pc-app
+cli/                  # yj-cli
+browser-extension/    # yj-browser-extension
+```
+
+```text
+{platform}/
+  scripts/            # platform-level only
+  {service_name}/     # one deployable / one app
+```
+
+- `backend/proto/` is reserved (see yj-backend-msa).
+- `browser-extension/native_{name}/` → **yj-backend-service**.
+- Do not invent new platform roots or put app code at repo root.
+- Do not add per-service `scripts/` or edit root Makefile for each new service.
+
+## Environment (guardrails only)
+
+Allowed files at each service root (no plain `.env`):
+
+`.env.local-dev` · `.env.development` · `.env.production` · `.env.examples`
+
+- Do not invent alternate names (including Vite `.env` / `.env.local`) unless a thin loader maps to this set.
+- Env field sets come from `templates/platform/<platform>/`. `browser-extension/native_*` uses the `backend-service` templates. Do not invent fields/filenames outside those templates.
+- `HOST`/`PORT` are only required when the service actually listens (e.g. backend MSA, frontend). For `backend-service` they are optional — add only if needed.
+- Commit `.env.examples` only; never commit the other three.
+- Local platform `run.*` uses `.env.local-dev` only — do not hardcode HOST/PORT in scripts.
+
+## Skill routing
+
+| Path | Platform skill |
+|------|----------------|
+| `backend/**` | `yj-backend-msa` |
+| `backend-service/**` | `yj-backend-service` |
+| `frontend/**` | `yj-frontend` |
+| `mobile-app/**` | `yj-mobile-app` |
+| `pc-app/**` | `yj-pc-app` |
+| `cli/**` | `yj-cli` |
+| `browser-extension/native_*/**` | `yj-backend-service` |
+| `browser-extension/**` (other) | `yj-browser-extension` |
+
+Never load all platform skills. Never apply a platform skill outside its folder.
+
+## Universal roles
+
+```text
+entry   = executable entrypoint + route/command/screen registration + wiring
+flow    = feature composition + dto / input-output shape
+domain  = model + repository + rules (only where persistence lives)
+view    = UI (only platforms that render UI)
+infra   = shared technical modules (config, clients, logging, utils)
+```
+
+UI clients default to **no `domain`**: model = API types; rules live in flow.
+
+## Import direction
+
+Allowed: `entry -> flow -> domain -> infra`, `entry -> infra`, `flow -> infra`, `view -> flow`, `domain -> infra`.
+
+Forbidden: `domain -> flow/entry/other domain`, `flow -> entry/other flow` (unless repo allows), `infra -> *`, `view -> domain/infra/network`, generated UI → project-specific imports.
+
+Cycles are structure bugs — do not paper over with lazy imports or wrappers.
+
+## Editing workflow
+
+Before: platform skill → feature/domain → minimal file set → prefer reuse.
+
+During: edit in place; no thin wrappers/adapters; no one-line functions unless the name is a real domain concept; keep feature work and drive-by refactors separate.
+
+Avoid names: `{entity}_v2|_wrapper|_adapter|_helper`, `{feature}_manager|_processor`.
+
+Avoid layers unless user requests: `usecases/`, `workflows/`, `orchestrations/`, `application/`, `controllers/`, `handlers/`.
+
+`flow` is the composition layer — do not invent a layer above it.
+
+After: summarize files, boundaries, new files, test/migration risk briefly.
+
+## Cross-platform contracts
+
+- Prefer generated clients / `backend/proto/dist/{lang}` over hand-copied DTOs.
+- Do not import another platform's source tree.
+- Do not read unrelated platforms unless the user task explicitly spans them.

yjcli/data/skills/yj-backend-msa/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: yj-backend-msa
+description: >-
+  Backend MSA architecture with mandatory gRPC/protobuf. Use only when creating
+  or editing code under backend/. Language-agnostic (Go/Python/Java/etc.).
+  Covers backend/{service}, backend/proto, and proto/dist/{lang}. Do not use for
+  backend-service/, frontend/, mobile-app/, pc-app/, cli/, or browser-extension/.
+---
+
+# yj-backend-msa
+
+Requires `yj-arch-core`. Scope: **`backend/` only**.
+
+## Shape
+
+```text
+backend/
+  scripts/                 # platform-level only
+  proto/                   # owned by backend MSA only
+    *.proto
+    dist/
+      golang/
+      python/
+      java/
+      dart/
+      ...
+  {service_name}/
+    apps/                  # entry
+    services/              # flow
+    domains/               # domain
+    modules/               # infra
+```
+
+- One `{service_name}` = one deployable microservice.
+- Do not over-split domains into tiny services. Split by cohesive business capability.
+- gRPC + protobuf are **mandatory**. External API surface is proto, not ad-hoc JSON structs copied across services.
+
+## proto
+
+- Sources live only in `backend/proto/`.
+- Generated stubs go to `backend/proto/dist/{lang}/`.
+- Other platforms (e.g. `mobile-app`) may **symlink** to `backend/proto/dist/{lang}` — they must not own `.proto` copies.
+- Prefer package boundaries in proto that align with service boundaries.
+
+## Roles inside `{service_name}`
+
+```text
+entry  = apps/{app_name}/main.{ext}
+flow   = services/{feature}/dto.{ext} + service.{ext}
+domain = domains/{domain}/model.{ext} (+ repository/rules/errors/types)
+infra  = modules/{module}.{ext}
+```
+
+### entry
+
+- Init, gRPC server registration, dependency wiring only.
+- No business logic. No direct domain calls (always through flow).
+
+### flow
+
+- Feature/workflow composition. DTOs for this service's use of contracts.
+- Reuse services across RPCs; do not create a service per RPC automatically.
+- Do not import other services' source trees; call them over gRPC using generated clients.
+
+### domain
+
+File responsibilities:
+
+- `model.{ext}`: internal domain model, entity, schema, or data shape.
+- `repository.{ext}`: persistence and retrieval using the domain model.
+- `rules.{ext}`: domain-specific decision rules and pure validations (optional).
+- `errors.{ext}`: domain-specific errors or exceptions (optional).
+- `types.{ext}`: enums, value types, and domain-only type definitions (optional).
+
+Rules:
+
+- Persistence + rules for concepts this service owns.
+- No gRPC/transport types in domain.
+- Domains must not import apps or services.
+- No domain→domain imports; compose in flow.
+- Do not duplicate the same responsibility across multiple domains.
+
+### Relation domain
+
+When two domains are both first-class concepts and their relationship is managed directly, create a relation domain.
+
+Use when:
+
+- `{domain_a}` and `{domain_b}` are both first-class concepts.
+- Neither is merely a field of the other.
+- The relationship itself is created, deleted, queried, or constrained.
+- Multiple RPCs/routes express the same relationship from different perspectives.
+
+```text
+domains/{domain_a}/
+domains/{domain_b}/
+domains/{relation_domain}/
+services/{relation_feature}/
+  dto.{ext}
+  service.{ext}
+```
+
+- The relation domain owns relationship mechanics only.
+- It must not import the related domains directly.
+- Existence checks, policy checks, and cross-domain composition belong in the service (flow).
+
+### infra
+
+- config, db, logging, gRPC client factories, auth adapters, low-level helpers.
+- No business logic or domain-specific helpers.
+- Do not turn modules into a generic utilities dump.
+- Modules must not import apps, services, or domains.
+
+## Import direction
+
+```text
+entry -> flow -> domain -> infra
+entry -> infra
+flow  -> infra (including generated gRPC clients)
+```
+
+Forbidden: handler→domain, domain→flow, cross-service source imports, new layers above flow.
+
+## Editing scope
+
+- Touch one `{service_name}` plus, if needed, `backend/proto` (and regenerate dist).
+- Do not open `frontend/` or other platforms unless the user explicitly asks for a cross-change.