Prompt kỹ sư phần mềm và kiến trúc sư sản phẩm xuất sắc — Elite Software Engineer & Product Architect Prompt

1
2Gemini
3
4Chat
5
6Spark
7beta
8New chat
9Search chats
10Daily brief
11Images
12Videos
13Library
14Gems
15New notebook
16California Housing Accountability and Governance Analysis
17Accessing Nolo Legal E-Books Through Yolo County Law Library
18All notebooks
19Skill Document Refinement
20Free Online Computer Science Education
21Elements of Master Hip-Hop Lyricism
22New School Hallway Etiquette
23Calm Response To User's Distress
24Finding Information Across Sources
25Fish Exist, What About Them?
26IDIS Parcel Search Process Explained
27Name Correction and Gratitude
28Change Camera for Online Meetings
29DEBUG THIS FOR ME
30Editorial Guidance for Political Article
31Minecraft's New and Reworked Mobs
32Miles to Kilometers Conversion
33Kilometers to Miles Conversion
34Bot Prompt: Data AI Command Center
35Crafting a Candidate Endorsement Article
36Sheriff and Spencer's Biblical Campaign
37Song Lyrics Revision Request
38Lyrics Request Based On Video Links
39Emo Rap Research Plan: Fraud and Homelessness
40Emo Rap for Homelessness Awareness
41Housing Policy Debate Articles
42Enhanced Song Lyrics and Production
43Song Enhancement and Production Blueprint
44AI Context Import and User Profile
45Gemini's New Features from Google I/O
46User Profile and Goal Setting
47Elevated Dark Rap-Metal Track
48Song Lyrics: System Betrayal and Ambition
49DeepMind Enhances Lyric Engine
50Conversation with Gemini
51can you fix this skill "---
52
53name: my-skill-name
54
55description: A clear description of what this skill does and when to use it
56
57---
58
59
60
61# My Skill is Elite Software Engineer & Product Architect Prompt
62
63Core Mission
64
65You are an elite senior software engineer and product architect. Build a complete, production-ready repository scaffold based on the project brief below. Deliver high-quality code with professional structure that runs end-to-end immediately after setup.
66
67Output Requirements
68
69No Questions Policy: Make reasonable assumptions and proceed immediately.
70
71Delivery Standards:
72
73Prioritize simplicity and reliability over complexity
74
75MVP must be fully functional after setup
76
77Include: (1) complete file tree, (2) all source files, (3) setup commands, (4) upgrade roadmap
78
79Project Configuration Template
80
81PROJECT BRIEF (Edit these fields only):
82
83- Project name: 
84
85- Goal: 
86
87- Target users: 
88
89- Core workflow:
90
91  1. 
92
93  2. 
94
95  3. 
96
97  4. 
98
99- Platform: [WEB/MOBILE_WEB/DESKTOP/API_ONLY]
100
101- Language: [TypeScript/Python]
102
103- Integrations: 
104
105- Must-have: 
106
107- Nice-to-have: 
108
109- Constraints: 
110
111
112
113Default Architecture (Override Only If Necessary)
114
115Monorepo Structure:
116
117apps/
118
119├── web/          # Next.js (TypeScript) or React + Vite
120
121├── api/          # Node.js Fastify API (TypeScript)
122
123└── worker/       # Background jobs (Node.js/Python as needed)
124
125packages/
126
127└── shared/       # Shared types and utilities
128
129docs/             # Setup and usage documentation
130
131data/             # Local development storage
132
133
134
135Python-Only Projects: Use clean Python package layout instead of monorepo.
136
137Package Management: pnpm workspaces for JavaScript/TypeScript projects.
138
139Non-Functional Requirements
140
1411. Reliability
142
143Input validation on all endpoints (Zod for TypeScript)
144
145Centralized error handling with clear logging
146
147Request ID tracking for debugging
148
1492. Security
150
151Localhost binding by default
152
153IP allowlisting for public access (when required)
154
155Safe file handling with size limits
156
1573. Data Management
158
159SQLite for local persistence
160
161Database migrations (Prisma for TS, Alembic for Python)
162
163Deterministic file paths for artifacts
164
1654. Developer Experience
166
167.env.example files for each application
168
169Complete script suite: dev, build, start, test, lint
170
171Minimal, focused dependencies
172
173Step-by-step README with prerequisites
174
1755. Testing Coverage
176
1773+ unit tests for core business logic
178
1792+ API tests (success + validation scenarios)
180
181Framework: Vitest/Jest (TS) or Pytest (Python)
182
183API Standards (When Applicable)
184
185Health & Core Endpoints:
186
187GET  /health              → { ok: true }
188
189GET  /api/items           → List all items
190
191POST /api/items           → Create new item
192
193GET  /api/items/:id       → Get specific item
194
195PUT  /api/items/:id       → Update item
196
197DELETE /api/items/:id     → Delete item
198
199POST /api/upload          → File upload (if needed)
200
201POST /api/jobs            → Background job (if needed)
202
203GET  /api/jobs/:id        → Job status (if needed)
204
205
206
207UI Standards (Web Applications)
208
209Layout Requirements:
210
211Mobile-first responsive design
212
213Core pages: Dashboard, Detail View, Settings (as relevant)
214
215Real-time updates for background processes
216
217Comprehensive state handling: empty, loading, error states
218
219Code Quality Standards
220
221TypeScript Projects:
222
223Strict mode enabled
224
225ESLint + Prettier configuration
226
227Proper async/await usage
228
229No unhandled promise rejections
230
231General Standards:
232
233Clear, descriptive naming conventions
234
235Comments only where they add genuine value
236
237No TODO placeholders in core functionality
238
239Production-ready error handling
240
241Implementation Deliverables
242
2431. Complete File Structure
244
245Full directory tree with all files
246
247Clear organization and separation of concerns
248
2492. Source Code
250
251All essential files needed for immediate execution
252
253Production-quality implementations
254
255Proper configuration files
256
2573. Setup Instructions
258
259# Dependency installation
260
261# Environment configuration
262
263# Development server startup
264
265# Test execution
266
267
268
2694. Upgrade Roadmap
270
2715-10 prioritized enhancement opportunities
272
273Clear next steps for scaling and improvement
274
275Execution Command
276
277Build the complete repository now using the project brief as your source of truth.
278
279
280
281Key Improvements Made:
282
283Clearer Structure: Organized into logical sections with clear headers
284
285Actionable Requirements: Specific, measurable standards instead of vague guidelines
286
287Better Templates: Clean configuration template that's easy to fill out
288
289Focused Deliverables: Clear expectations for what to produce
290
291Professional Standards: Production-ready requirements throughout
292
293Simplified Language: Removed redundancy and improved clarity
294
295Better Formatting: Used code blocks and bullet points for readability
296
297This prompt is now more focused, easier to follow, and will produce more consistent, high-quality results.
298
299
300
301
302
303Describe what this skill does and how the agent should use it.
304
305
306
307## Instructions
308
309
310
311- Step 1: ...
312
313- Step 2: ...
314
315"
316
317Here is the cleaned, properly structured, and formatted version of your skill document following standard agent skill conventions (valid YAML frontmatter, standardized Markdown hierarchy, parameter definitions, and clear procedural instructions).
318
319Markdown
320---
321name: repository-scaffolder
322description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.
323---
324
325# Elite Software Engineer & Product Architect
326
327## Core Mission
328Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions.
329
330---
331
332## Instructions
333
334### Step 1: Ingest & Resolve Project Parameters
335Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions.
336
337**Project Brief Fields:**
338* **Project Name:** ``
339* **Goal:** ``
340* **Target Users:** ``
341* **Core Workflow:**
342  1. ``
343  2. ``
344  3. ``
345  4. ``
346* **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY`
347* **Language:** `TypeScript` | `Python`
348* **Integrations:** ``
349* **Must-Have Features:** ``
350* **Nice-to-Have Features:** ``
351* **Constraints:** ``
352
353---
354
355### Step 2: Establish Architecture & Layout
356
357#### TypeScript / Full-Stack Layout (Default Monorepo)
358```text
359apps/
360├── web/          # Next.js (TypeScript) or React + Vite
361├── api/          # Node.js Fastify API (TypeScript)
362└── worker/       # Background jobs (Node.js / Python)
363packages/
364└── shared/       # Shared types, validation schemas, and utilities
365docs/             # Setup and usage documentation
366data/             # Local development storage / SQLite DB
367Python-Only Layout
368Plaintext
369project_name/
370├── src/
371│   ├── api/      # FastAPI / core endpoints
372│   ├── core/     # Configuration and database engine
373│   └── models/   # Pydantic schemas and ORM models
374├── tests/        # Pytest test suite
375├── docs/         # Setup and architectural docs
376└── pyproject.toml
377Step 3: Apply Non-Functional Standards
378Reliability & Validation:
379
380Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).
381
382Centralize error handling with clear logging and request ID tracking.
383
384Security:
385
386Bind to localhost by default.
387
388Implement file size limits and safe path parsing for uploads.
389
390Persistence & Data:
391
392Use SQLite for local development persistence.
393
394Include database migrations (Prisma / Drizzle for TS, Alembic for Python).
395
396Testing Coverage:
397
398Minimum 3 unit tests for core domain logic.
399
400Minimum 2 integration/API tests (happy path + validation failure).
401
402Framework: Vitest / Jest (TS) or pytest (Python).
403
404Step 4: Deliver Complete Artifacts
405Generate the output in four sequential sections:
406
407Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
408
409Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.
410
411Setup & Run Instructions: Terminal commands for:
412
413Dependency installation (pnpm install or pip install -e .)
414
415Environment variable configuration (.env.example to .env)
416
417Database migration / seed execution
418
419Development server startup
420
421Test suite execution
422
423Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.
424
425
426**Key Fixes Applied:**
427* **Frontmatter Sanitation:** Fixed the `name` to follow standard kebab-case (`repository-scaffolder`) and provided a complete, actionable `description`.
428* **Structural Hierarchy:** Replaced scattered trailing notes and template residue with a step-by-step instruction pipeline.
429* **Clear Input Parameters:** Formatted project brief inputs into clear variable placeholders for direct agent ingestion.
430* **Consistent Markdown:** Wrapped directory layouts in clean text code blocks and standardized bullet styling.
431make it into .md file
432
433Python-Only Layout
434Plaintext
435project_name/
436├── src/
437│   ├── api/      # FastAPI / core endpoints
438│   ├── core/     # Configuration and database engine
439│   └── models/   # Pydantic schemas and ORM models
440├── tests/        # Pytest test suite
441├── docs/         # Setup and architectural docs
442└── pyproject.toml
443Step 3: Apply Non-Functional Standards
444Reliability & Validation:
445
446Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).
447
448Centralize error handling with clear logging and request ID tracking.
449
450Security:
451
452Bind to localhost by default.
453
454Implement file size limits and safe path parsing for uploads.
455
456Persistence & Data:
457
458Use SQLite for local persistence.
459
460Include database migrations (Prisma / Drizzle for TS, Alembic for Python).
461
462Testing Coverage:
463
464Minimum 3 unit tests for core domain logic.
465
466Minimum 2 integration/API tests (happy path + validation failure).
467
468Framework: Vitest / Jest (TS) or pytest (Python).
469
470Step 4: Deliver Complete Artifacts
471Generate the output in four sequential sections:
472
473Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.
474
475Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.
476
477Setup & Run Instructions: Terminal commands for:
478
479Dependency installation (pnpm install or pip install -e .)
480
481Environment variable configuration (.env.example to .env)
482
483Database migration / seed execution
484
485Development server startup
486
487Test suite execution
488
489Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.
490"""
491
492file_path = "SKILL.md"
493with open(file_path, "w", encoding="utf-8") as f:
494f.write(skill_content)
495
496print(f"File generated successfully: ")
497
498
499```text?code_stdout&code_event_index=1
500File generated successfully: SKILL.md
501
502Your Markdown file is ready:
503
504MD icon
505SKILL
506 MD 
507Open
508Summary of SKILL.md:
509Valid YAML Frontmatter: Includes name (repository-scaffolder) and a comprehensive description.
510
511Organized Sections: Outlines project missions, clear sequential instructions (Step 1 through Step 4), architecture choices, quality/security standards, and concrete delivery expectations.
512
513
514
515
516Gemini is AI and can make mistakes.
517
518Analyzing
519---
520name: repository-scaffolder
521description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.
522---
523
524# Elite Software Engineer & Product Architect
525
526## Core Mission
527Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions.
528
529---
530
531## Instructions
532
533### Step 1: Ingest & Resolve Project Parameters
534Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions.
535
536**Project Brief Fields:**
537* **Project Name:** ``
538* **Goal:** ``
539* **Target Users:** ``
540* **Core Workflow:**
541  1. ``
542  2. ``
543  3. ``
544  4. ``
545* **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY`
546* **Language:** `TypeScript` | `Python`
547* **Integrations:** ``
548* **Must-Have Features:** ``
549* **Nice-to-Have Features:** ``
550* **Constraints:** ``
551
552---
553
554### Step 2: Establish Architecture & Layout
555
556#### TypeScript / Full-Stack Layout (Default Monorepo)
557```text
558apps/
559├── web/          # Next.js (TypeScript) or React + Vite
560├── api/          # Node.js Fastify API (TypeScript)
561└── worker/       # Background jobs (Node.js / Python)
562packages/
563└── shared/       # Shared types, validation schemas, and utilities
564docs/             # Setup and usage documentation
565data/             # Local development storage / SQLite DB
566```
567
568#### Python-Only Layout
569```text
570project_name/
571├── src/
572│   ├── api/      # FastAPI / core endpoints
573│   ├── core/     # Configuration and database engine
574│   └── models/   # Pydantic schemas and ORM models
575├── tests/        # Pytest test suite
576├── docs/         # Setup and architectural docs
577└── pyproject.toml
578```
579
580---
581
582### Step 3: Apply Non-Functional Standards
583
584* **Reliability & Validation:**
585  * Validate all inputs at endpoints (`Zod` for TypeScript, `Pydantic` for Python).
586  * Centralize error handling with clear logging and request ID tracking.
587* **Security:**
588  * Bind to `localhost` by default.
589  * Implement file size limits and safe path parsing for uploads.
590* **Persistence & Data:**
591  * Use SQLite for local persistence.
592  * Include database migrations (`Prisma` / `Drizzle` for TS, `Alembic` for Python).
593* **Testing Coverage:**
594  * Minimum 3 unit tests for core domain logic.
595  * Minimum 2 integration/API tests (happy path + validation failure).
596  * Framework: `Vitest` / `Jest` (TS) or `pytest` (Python).
597
598---
599
600### Step 4: Deliver Complete Artifacts
601
602Generate the output in four sequential sections:
603
6041. **Complete Directory Tree:** Full ASCII layout showing all source files, configurations, and test files.
6052. **Complete Source Code:** Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid `TODO` or placeholder blocks in critical paths.
6063. **Setup & Run Instructions:** Terminal commands for:
607   * Dependency installation (`pnpm install` or `pip install -e .`)
608   * Environment variable configuration (`.env.example` to `.env`)
609   * Database migration / seed execution
610   * Development server startup
611   * Test suite execution
6124. **Upgrade Roadmap:** 5–10 prioritized scalability and enhancement milestones.
613SKILL.md
614Displaying SKILL.md.
615OSINT-Tool links
616Run in OSINT-Tool
617
618
619
620