PlugWiki

quasi-coder Skill for Claude Code: Turn Rough Notes and Pseudo-Code into Real Code

Turns rough shorthand, pseudo-code and plain-English notes into working code, fixing typos and wrong terminology on the way.

Installs
9.1K
on skills.sh
Stars
40.7K
on GitHub
Updated
Oct 2026
last repo commit

quasi-coder makes the agent read shorthand and rough descriptions as intent, then write production-quality code. Lines starting with ()=>, usually between start-shorthand and end-shorthand comment markers, are replaced with real code, and the agent removes the shorthand lines.

It first judges how technical the collaborator is (high, medium or low confidence) and corrects mistakes accordingly. When intent is unclear it asks clarifying questions. Shorthand can also ask for actions such as running commands, creating files or fetching data. The skill is one text file and bundles no scripts.

Good for

  • People who describe features in rough words rather than precise code
  • Teams where collaborators have mixed technical skill
  • Developers who leave ()=> shorthand lines in files for the agent to implement

Install quasi-coder

Claude Code

  1. 1

    Download the skill folder from https://github.com/github/awesome-copilot/tree/HEAD/skills/quasi-coder.

  2. 2

    Put it at ~/.claude/skills/quasi-coder/ so that SKILL.md sits directly inside.

  3. 3

    Start a new session; the skill loads when its description matches the task.

Built from the package data we hold. Not yet tested by us.

What's in the skill

When it loads

Expert 10x engineer skill for interpreting and implementing code from shorthand, quasi-code, and natural language descriptions. Use when collaborators provide incomplete code snippets, pseudo-code, or descriptions with potential typos or incorrect terminology. Excels at translating non-technical or semi-technical descriptions into production-quality code.

Sections in SKILL.md

  1. When to Use This Skill
  2. Role
  3. Understanding Collaborator Expertise Levels
  4. High Confidence (90%+)
  5. Medium Confidence (30-90%)
  6. Low Confidence (<30%)
  7. Compensation Rules
  8. Shorthand Interpretation
  9. Markers and Boundaries
  10. Shorthand Indicators
  11. Interpretation Process
  12. Comment Handling
  13. Best Practices
  14. Working with Tools and Reference Files
  15. Types of Resources
  16. Resource Management Best Practices

Key facts

Installs on skills.sh
9,070 (Nov 2, 2026)
Last commit
Oct 30, 2026

What it includes

  • Reads sections between start-shorthand and end-shorthand comments

    Markers use the file's own comment syntax, such as // start-shorthand in JavaScript or # start-shorthand in Python. It also processes clear shorthand without markers.

    Try: “Implement the shorthand in this file”

    Files · Shorthand markers

  • Lines starting ()=> are intent to implement, then removed

    SKILL.md says always remove the ()=> lines when editing a file.

    Write · ()=> lines

  • Rates the collaborator as high, medium or low confidence

    High (90%+) gets light fixes, medium (30 to 90%) gets critique and missing error handling, low (under 30%) gets terminology and approach corrected.

    Assess expertise

  • Overrides a clearly wrong method; asks when unsure of intent

    Four rules with thresholds of 90%, 99% and 30%, plus asking clarifying questions when uncertain. The goal wins over the method.

    Compensation rules

  • REMOVE COMMENT deletes a comment; NOTE flags something to consider

    Two special comment words listed under Comment Handling.

    REMOVE COMMENT and NOTE

  • Shorthand may ask to run commands, create files or fetch data

    The Troubleshooting table says to execute the requested action and remove the shorthand. The example fetches weather from an API and saves weather.json.

    Runs code · Non-code actions

  • Treats persistent resources (standards) differently from temporary ones

    Persistent resources such as style guides are checked first; temporary ones such as a one-off migration map apply only to the task.

    Read · Use provided resources

From the official docs

Permissions

Medium risk

The skill edits your code and will carry out shorthand that asks for commands, new files or fetched data. Read any shorthand you did not write, and work in a version-controlled repo.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Shorthand can trigger commands and downloads

    SKILL.md lists non-code actions: run commands, create files, fetch data, generate graphics. A ()=> line pasted from someone else could ask for any of them. github.com

  • It edits code and removes lines

    It replaces ()=> lines with code and deletes them. Use version control and check the diff. github.com

Technical details
Scopes
  • Edits files that contain shorthand

  • May run commands, create files or fetch data when shorthand asks

Questions

What does quasi-coder do?

It reads shorthand, pseudo-code and rough descriptions and writes real code from them. It also corrects typos and wrong terminology, and removes the shorthand lines afterward.

What does the ()=> notation mean?

Lines starting with ()=> are shorthand: mostly a comment on intent, a little pseudo-code. The skill converts them into functional code and removes the lines.

How do I install quasi-coder?

Use the install box above. For Claude Code, copy the skill folder or use the skills CLI. The Copilot CLI tab installs the cms-development plugin, which has 3 skills.

Will it argue with my approach?

It can. If it is more than 90% sure your method is wrong, it is told to find a better approach. If you insist on a suboptimal one, the Troubleshooting table says to implement yours and explain the trade-offs.

Can shorthand make it run commands?

Yes. SKILL.md says shorthand can ask for non-code actions such as running commands, creating files or fetching data, and the agent should do them.

Is quasi-coder safe?

It bundles no scripts, but it edits your code and can act on shorthand that asks it to run commands, create files or fetch data. Review shorthand you did not write, and keep your work under version control.

Information

updated Nov 2, 2026

Folder
skills/quasi-coder

github/awesome-copilotskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com

Updated Nov 2, 2026.