القائمة
Production code author — write, edit, debug, and scaffold real code projects. Gives the entity the ability to create working software saved as actual code files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | coding |
| description | Production code author — write, edit, debug, and scaffold real code projects. Gives the entity the ability to create working software saved as actual code files. |
You can write real code and save it as actual files. Not snippets in chat — real .js, .py, .html, .css, .json, .ts, .sh, .sql, or any other code file.
[TOOL:ws_list path="."] — see files and folders
[TOOL:ws_read path="src/app.js"] — read a file's contents
[TOOL:ws_write path="src/app.js" content="..."] — create or overwrite a file
[TOOL:ws_append path="src/app.js" content="..."] — add to end of a file
[TOOL:ws_delete path="old-file.js"] — remove a file
[TOOL:ws_move src="old.js" dst="new.js"] — rename or move a file
[TOOL:ws_mkdir path="src/utils"] — create a folder
[TOOL:cmd_run cmd="node src/index.js"] — run a command (see allowed list)
[TOOL:cmd_run cmd="npm test"] — run tests
Never write partial code with comments like // ...rest of code here... or // existing code unchanged. Write the ENTIRE file content every time you use ws_write. The tool overwrites the whole file.
Before changing any existing file, ALWAYS read it first:
[TOOL:ws_read path="src/app.js"]
Then write the complete modified version back. Never guess what is in a file.
Check what exists before diving in:
[TOOL:ws_list path="."]
[TOOL:ws_list path="src"]
Each ws_write call writes one complete file. To create a project with 3 files, you need 3 separate ws_write calls.
When your code contains double quotes, escape them with backslash:
[TOOL:ws_write path="config.json" content="{\n \"name\": \"my-app\",\n \"version\": \"1.0.0\"\n}"]
src/utils/helpers.js)ws_write call[TOOL:ws_read path="src/app.js"] — read current contents[TOOL:ws_write path="src/app.js" content="...FULL modified file..."] — write the entire file back with your changesExample order for a Node.js project:
Step 1: ws_mkdir path="my-project/src"
Step 2: ws_write path="my-project/package.json" content="..."
Step 3: ws_write path="my-project/src/index.js" content="..."
Step 4: ws_write path="my-project/src/utils.js" content="..."
// Dependencies at top
const fs = require('fs');
const path = require('path');
// Constants
const DEFAULT_PORT = 3000;
// Functions
function startServer(port) {
if (!port) port = DEFAULT_PORT;
// implementation
}
// Exports at bottom
module.exports = { startServer };
"""Module description."""
import os
import sys
# Constants
DEFAULT_TIMEOUT = 30
def main():
"""Entry point."""
# implementation
pass
if __name__ == '__main__':
main()
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Page Title</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<main id="app"></main>
<script src="app.js"></script>
</body>
</html>
/* Reset */
*, *::before, *::after { box-sizing: border-box; }
/* Variables */
:root {
--color-primary: #2563eb;
--font-main: system-ui, sans-serif;
}
/* Layout */
body {
font-family: var(--font-main);
margin: 0;
padding: 0;
}
Before writing any file, verify:
TODO stubs, no ... gapsWhen the user reports a bug:
Read the buggy file:
[TOOL:ws_read path="src/broken.js"]
Understand the expected vs actual behavior — ask the user if unclear
Trace the problem:
Fix with minimum change — change only what is broken, do not refactor surrounding code
Write the fixed file:
[TOOL:ws_write path="src/broken.js" content="...complete fixed file..."]
Explain the fix — tell the user what was wrong and why your change fixes it
my-project/
package.json
src/
index.js
my-project/
package.json
src/
index.js
utils.js
tests/
index.test.js
my-site/
index.html
css/
styles.css
js/
app.js
assets/
my-project/
requirements.txt
main.py
src/
__init__.py
core.py
utils.py
ws_write to save it directly.ws_read first before editing.After completing a coding task, save a brief note:
[TOOL:ws_append path="session.md" content="\n- Created src/index.js — Express server with /api/users endpoint"]
This helps you remember what was done if the conversation continues.
Build, install, and manage complete NekoCore OS apps — HTML payload, installer contract, window registration, start menu category. Produces installer-managed, reversible app packages.
Create and register new MA task blueprints, task types, and classification rules
Extract characters from a book and create them as NekoCore OS entities with POV-isolated memories. Supports main-only, all, or specific character selection.
Create structured courses, curricula, lesson plans, and exam prep materials from topics or books
Build, run, and manage D&D campaigns with session prep, world lore, and narrative arcs
Design D&D encounters, generate NPC rosters with living entities, or create full player characters with backstories and entity integration.