원클릭으로 Manus에서 모든 스킬 실행

ry-newp

스타1

포크0

업데이트2026년 6월 15일 12:18

Дизайн нового проекта: скептические вопросы, research, архитектура, ТЗ, ADR. Используй для: новый проект, ТЗ, проект с нуля, спроектируй, ARCHITECTURE.md. EN triggers: ry-newp, new project, design project from scratch, requirements, architecture docs, scaffold project, MADR ADR.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

NDDev-it-com

NDDev-it-com/rldyour-opencode

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

ry-newp

Purpose

Design a new project with enough rigor that implementation can start with clear architecture, technology choices, business logic, quality gates, and delivery plan.

Workflow

Gather all provided context: prompt, docs, chats, requirements, screenshots, business constraints.
Ask skeptical Russian questions with options. Cover product scope, users, business logic, data, integrations, security, deployment, observability, tests, and constraints.
Research current best technologies and architecture patterns with ry-explore. Prefer Context7 MCP for official versioned framework docs, DeepWiki MCP for reference repo architecture, Grep MCP for real production patterns, and web-research for current landscape.
Use Sequential Thinking MCP (sequential-thinking_*) for non-trivial architecture and technology decisions.
Write planning docs under .serena/newproj/<project>/ using references/flow-lifecycle.md as the lifecycle contract reference.
Ask for approval before creating any scaffold code.
If scaffold is approved, create the minimal useful project structure, commit atomically with Conventional Commits, and initialize Serena memories with verified facts only.

Serena Memory Seeds

After scaffold approval and the first real commit, initialize Serena memories from verified project facts only. At minimum seed CONTEXT-01-CORE.md for current source-of-truth facts and FUTURE-01-VISION.md for future-shape constraints. Propose ADR memories for non-obvious decisions, but do not write ADR meaning without explicit owner approval.

Output

Produce English project documents and Russian user-facing summaries.

Default docs:

HLO: high-level overview - one-paragraph purpose, users, value.
Requirements: functional and non-functional, with acceptance criteria.
Architecture: layers, modules, data flow, integration points, deployment topology.
ADRs: architecture decision records for each non-obvious choice with context, decision, and consequences.
Tech stack: languages, frameworks, libraries, MCP servers, tooling - with version constraints and rationale.
API: endpoints, payloads, auth, error contracts.
Data: entities, fields, relationships, indexes, migrations strategy.
Infra: hosting, CI/CD, environments, observability.
Security: threat model, auth/authz, input validation, secrets management.
Testing: unit, integration, E2E strategy, coverage targets.
Structure: directory layout with purpose per directory.
Conventions: naming, commits, branching, code style, review process.
Delivery plan: milestones, dependencies, risk mitigation.

Each doc must be grounded in research evidence, not speculation. Link to sources for technology choices.

이 저장소의 다른 Skills

같은 저장소

browser-debug

NDDev-it-com/rldyour-opencode

Отлаживает browser-only failures через управляемые Chrome DevTools MCP и Playwright CLI. Используй для: консоль, сеть, runtime, hydration, layout, memory, performance, Lighthouse. EN triggers: browser debug, console errors, network, runtime, layout, memory, performance, Lighthouse.

2026-07-101

browser-tool-routing

NDDev-it-com/rldyour-opencode

Маршрутизирует browser tasks только через управляемые Playwright CLI и Chrome DevTools MCP. Используй для: проверь в браузере, UI, визуально, скриншот, Figma, консоль, сеть, перфоманс. EN triggers: browser routing, UI validation, screenshots, visual QA, console, network, performance.

2026-07-101

browser-validation

NDDev-it-com/rldyour-opencode

Валидация UI и пользовательских сценариев через управляемый Playwright CLI. Используй для: проверь UI, проверь в браузере, скриншот, регрессия, адаптив, бизнес-логика. EN triggers: validate UI, browser check, regression, responsive, business logic, screenshot.

2026-07-101

playwright-cli-validation

NDDev-it-com/rldyour-opencode

Низкоуровневая browser automation через управляемый Playwright CLI. Используй для: screenshots, snapshots, headed sessions, traces, responsive, UI proof. EN triggers: Playwright CLI validation, screenshots, snapshots, traces, responsive.

2026-07-101

visual-diff-review

NDDev-it-com/rldyour-opencode

Проводит visual QA для Figma, screenshots и reference images через управляемые browser providers. Используй для: pixel-perfect, сравни с Figma, сравни с фото, diff. EN triggers: visual diff, pixel-perfect, compare Figma, reference image.

2026-07-101

webwright-task

NDDev-it-com/rldyour-opencode

Совместимый маршрут legacy Webwright task intent в управляемые Playwright CLI и Chrome DevTools MCP; Webwright runtime не запускается. Используй для: найти, сравнить, выгрузить, повторить, reusable workflow. EN triggers: Webwright task, long-horizon web task, RPA, extraction, reusable workflow.

2026-07-101

name	ry-newp
description	Дизайн нового проекта: скептические вопросы, research, архитектура, ТЗ, ADR. Используй для: новый проект, ТЗ, проект с нуля, спроектируй, ARCHITECTURE.md. EN triggers: ry-newp, new project, design project from scratch, requirements, architecture docs, scaffold project, MADR ADR.

ry-newp

Purpose

Design a new project with enough rigor that implementation can start with clear architecture, technology choices, business logic, quality gates, and delivery plan.

Workflow

Gather all provided context: prompt, docs, chats, requirements, screenshots, business constraints.
Ask skeptical Russian questions with options. Cover product scope, users, business logic, data, integrations, security, deployment, observability, tests, and constraints.
Research current best technologies and architecture patterns with ry-explore. Prefer Context7 MCP for official versioned framework docs, DeepWiki MCP for reference repo architecture, Grep MCP for real production patterns, and web-research for current landscape.
Use Sequential Thinking MCP (sequential-thinking_*) for non-trivial architecture and technology decisions.
Write planning docs under .serena/newproj/<project>/ using references/flow-lifecycle.md as the lifecycle contract reference.
Ask for approval before creating any scaffold code.
If scaffold is approved, create the minimal useful project structure, commit atomically with Conventional Commits, and initialize Serena memories with verified facts only.

Serena Memory Seeds

Output

Produce English project documents and Russian user-facing summaries.

Default docs:

HLO: high-level overview - one-paragraph purpose, users, value.
Requirements: functional and non-functional, with acceptance criteria.
Architecture: layers, modules, data flow, integration points, deployment topology.
ADRs: architecture decision records for each non-obvious choice with context, decision, and consequences.
Tech stack: languages, frameworks, libraries, MCP servers, tooling - with version constraints and rationale.
API: endpoints, payloads, auth, error contracts.
Data: entities, fields, relationships, indexes, migrations strategy.
Infra: hosting, CI/CD, environments, observability.
Security: threat model, auth/authz, input validation, secrets management.
Testing: unit, integration, E2E strategy, coverage targets.
Structure: directory layout with purpose per directory.
Conventions: naming, commits, branching, code style, review process.
Delivery plan: milestones, dependencies, risk mitigation.

Each doc must be grounded in research evidence, not speculation. Link to sources for technology choices.