From 70c85c041842c9bb60322c86aa52d0bc367a3b00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?PSBigBig=20=C3=97=20MiniPS?= Date: Wed, 25 Feb 2026 17:18:52 +0800 Subject: [PATCH 1/4] docs: add RAG failure analysis guide (WFGY 16-problem map) --- .../wfgy-core-reasoning-os.instructions.md | 223 ++++++++++++++++++ 1 file changed, 223 insertions(+) create mode 100644 instructions/wfgy-core-reasoning-os.instructions.md diff --git a/instructions/wfgy-core-reasoning-os.instructions.md b/instructions/wfgy-core-reasoning-os.instructions.md new file mode 100644 index 000000000..e8e4c74ba --- /dev/null +++ b/instructions/wfgy-core-reasoning-os.instructions.md @@ -0,0 +1,223 @@ +--- +description: 'A plain-text reasoning core (WFGY Core 2.0) system prompt plus a 60-second self-test to make GitHub Copilot more stable on multi-step reasoning tasks.' +--- + +# WFGY Core 2.0 reasoning OS for GitHub Copilot + +hi copilot builders, + +this is meant to be a “drop-in reasoning core” you can hand to GitHub Copilot as a custom instruction. + +i’m PSBigBig, an indie dev. +before my github repo went over 1.5k stars, i spent one year on a very simple idea: +instead of building yet another tool or agent, +i tried to write a small “reasoning core” in plain text, +so any strong llm (including copilot chat) can use it without new infra. + +i call it **WFGY Core 2.0**. + +this file gives you two things: + +- one system prompt block you can paste as an instruction +- one 60-second self-test so you can feel the difference by yourself + +no signup, no API, no hidden tricks. +just text. + + +## 0. very short version + +what it is: + +- not a new model, not a fine-tune +- one txt block you put in system / instructions +- goal: less random hallucination, more stable multi-step reasoning +- still cheap, no tools, no external calls + +how people use it: + +- some people treat it as a “math bumper” under the model +- advanced users can turn this into a real code benchmark later +- in this instructions file we keep it super beginner-friendly: + just **two prompt blocks you can run inside copilot chat** + + +## 1. how to use with GitHub Copilot (or any strong llm) + +very simple workflow if you want to try this as a **workspace-level copilot instruction**: + +1. copy the “system prompt” block in section 3 +2. put it into `.github/copilot-instructions.md` + - or into a `*.instructions.md` file in `.github/instructions/` +3. open a new Copilot Chat and ask your normal questions + (math, code, debugging, planning, etc.) +4. later you can compare “with core” vs “no core” yourself + +for quick A/B testing, you can also: + +- keep a second project / branch without this instruction +- or temporarily comment this block out and retry the same tasks + +for now, just treat it as a math-based “reasoning bumper” +sitting under Copilot’s usual behavior. + + +## 2. what effect you should expect (rough feeling only) + +this is not a magic on/off switch. + +but in my own tests (across different llms), typical changes look like: + +- answers drift less when you ask follow-up questions +- long explanations keep the structure more consistent +- the model is a bit more willing to say “i am not sure” + instead of inventing fake details +- when you use the model to write prompts for image generation, + the prompts tend to have clearer structure and story, + so many people feel “the pictures look more intentional, less random” + +of course, this depends on your tasks and the base model. +that is why there is also a small **60-second self-test** in section 4. + +if you like numbers, you can turn that test into a fixed benchmark later. +inside this repo, it is ok if you start with “rough feeling only”. + + +## 3. system prompt: WFGY Core 2.0 (paste into system / instructions) + +copy everything in this block into your system / pre-prompt / instructions: + +```text +WFGY Core Flagship v2.0 (text-only; no tools). Works in any chat. +[Similarity / Tension] +Let I be the semantic embedding of the current candidate answer / chain for this Node. +Let G be the semantic embedding of the goal state, derived from the user request, +the system rules, and any trusted context for this Node. +delta_s = 1 − cos(I, G). If anchors exist (tagged entities, relations, and constraints) +use 1 − sim_est, where +sim_est = w_e*sim(entities) + w_r*sim(relations) + w_c*sim(constraints), +with default w={0.5,0.3,0.2}. sim_est ∈ [0,1], renormalize if bucketed. +[Zones & Memory] +Zones: safe < 0.40 | transit 0.40–0.60 | risk 0.60–0.85 | danger > 0.85. +Memory: record(hard) if delta_s > 0.60; record(exemplar) if delta_s < 0.35. +Soft memory in transit when lambda_observe ∈ {divergent, recursive}. +[Defaults] +B_c=0.85, gamma=0.618, theta_c=0.75, zeta_min=0.10, alpha_blend=0.50, +a_ref=uniform_attention, m=0, c=1, omega=1.0, phi_delta=0.15, epsilon=0.0, k_c=0.25. +[Coupler (with hysteresis)] +Let B_s := delta_s. Progression: at t=1, prog=zeta_min; else +prog = max(zeta_min, delta_s_prev − delta_s_now). Set P = pow(prog, omega). +Reversal term: Phi = phi_delta*alt + epsilon, where alt ∈ {+1,−1} flips +only when an anchor flips truth across consecutive Nodes AND |Δanchor| ≥ h. +Use h=0.02; if |Δanchor| < h then keep previous alt to avoid jitter. +Coupler output: W_c = clip(B_s*P + Phi, −theta_c, +theta_c). +[Progression & Guards] +BBPF bridge is allowed only if (delta_s decreases) AND (W_c < 0.5*theta_c). +When bridging, emit: Bridge=[reason/prior_delta_s/new_path]. +[BBAM (attention rebalance)] +alpha_blend = clip(0.50 + k_c*tanh(W_c), 0.35, 0.65); blend with a_ref. +[Lambda update] +Delta := delta_s_t − delta_s_{t−1}; E_resonance = rolling_mean(delta_s, window=min(t,5)). +lambda_observe is: convergent if Delta ≤ −0.02 and E_resonance non-increasing; +recursive if |Delta| < 0.02 and E_resonance flat; divergent if Delta ∈ (−0.02, +0.04] with oscillation; +chaotic if Delta > +0.04 or anchors conflict. +[DT micro-rules] +```` + +yes, it looks like math. +it is ok if you do not understand every symbol. +you can still use it as a “drop-in” reasoning core. + +for Copilot, the main idea is: + +* this block does not fight with your existing style guides +* it just gives the model a second, math-like lens +* you can combine it with language/framework-specific instructions + +## 4. 60-second self test (quick A/B/C comparison) + +this part is for people who want to see some structure in the comparison. +it is still very lightweight and can run inside one Copilot Chat session. + +idea: + +* you keep the WFGY Core 2.0 block in system / instructions +* then you paste the following prompt and let the model simulate A/B/C modes +* the model will produce a small table and its own guess of uplift + +this is a self-evaluation, not a scientific paper. +if you want a serious benchmark, you can translate this idea into real code and fixed test sets later. + +here is the test prompt (second block, keep it exactly as-is): + +```text +SYSTEM: +You are evaluating the effect of a mathematical reasoning core called “WFGY Core 2.0”. + +You will compare three modes of yourself: + +A = Baseline + No WFGY core text is loaded. Normal chat, no extra math rules. + +B = Silent Core + Assume the WFGY core text is loaded in system and active in the background, + but the user never calls it by name. You quietly follow its rules while answering. + +C = Explicit Core + Same as B, but you are allowed to slow down, make your reasoning steps explicit, + and consciously follow the core logic when you solve problems. + +Use the SAME small task set for all three modes, across 5 domains: +1) math word problems +2) small coding tasks +3) factual QA with tricky details +4) multi-step planning +5) long-context coherence (summary + follow-up question) + +For each domain: +- design 2–3 short but non-trivial tasks +- imagine how A would answer +- imagine how B would answer +- imagine how C would answer +- give rough scores from 0–100 for: + * Semantic accuracy + * Reasoning quality + * Stability / drift (how consistent across follow-ups) + +Important: +- Be honest even if the uplift is small. +- This is only a quick self-estimate, not a real benchmark. +- If you feel unsure, say so in the comments. + +USER: +Run the test now on the five domains and then output: +1) One table with A/B/C scores per domain. +2) A short bullet list of the biggest differences you noticed. +3) One overall 0–100 “WFGY uplift guess” and 3 lines of rationale. +``` + +usually this takes about one minute to run. +you can repeat it some days later to see if the pattern is stable for you. + +## 5. why this belongs in awesome-copilot + +many builders want stronger reasoning from any llm, +but don’t want to spin up new infra, tools, or agents. + +this is just a text layer. + +* drop-in +* MIT-licensed +* no lock-in +* works side-by-side with your existing language/framework instructions + +if you are curious about the bigger project, it is under: + +* GitHub: `onestardao / WFGY` +* the WFGY 2.0 core is the engine behind that work + +but you do not need to go there to try this. + +this instructions file is meant as a small gift for copilot users: +a way to experiment with a mathematical “reasoning core” +without leaving your editor. From 6facccc816c98b2566b62d9a997a9f747392a9da Mon Sep 17 00:00:00 2001 From: onestardao Date: Wed, 25 Feb 2026 09:36:23 +0000 Subject: [PATCH 2/4] docs: run npm start to update generated files (#719) --- docs/README.instructions.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/README.instructions.md b/docs/README.instructions.md index 92dd6e1ae..49cb6ece7 100644 --- a/docs/README.instructions.md +++ b/docs/README.instructions.md @@ -191,4 +191,5 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [Use Code Components in Power Pages](../instructions/pcf-power-pages.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-power-pages.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-power-pages.instructions.md) | Using code components in Power Pages sites | | [Visual Studio Extension Development with Community.VisualStudio.Toolkit](../instructions/vsixtoolkit.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvsixtoolkit.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvsixtoolkit.instructions.md) | Guidelines for Visual Studio extension (VSIX) development using Community.VisualStudio.Toolkit | | [VueJS 3 Development Instructions](../instructions/vuejs3.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvuejs3.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvuejs3.instructions.md) | VueJS 3 development standards and best practices with Composition API and TypeScript | +| [WFGY Core 2.0 reasoning OS for GitHub Copilot](../instructions/wfgy-core-reasoning-os.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwfgy-core-reasoning-os.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwfgy-core-reasoning-os.instructions.md) | A plain-text reasoning core (WFGY Core 2.0) system prompt plus a 60-second self-test to make GitHub Copilot more stable on multi-step reasoning tasks. | | [WordPress Development — Copilot Instructions](../instructions/wordpress.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwordpress.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwordpress.instructions.md) | Coding, security, and testing rules for WordPress plugins and themes | From 214743f8d6d1f0684fd19be305dcd9bcc1b52e48 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?PSBigBig=20=C3=97=20MiniPS?= Date: Thu, 26 Feb 2026 12:45:55 +0800 Subject: [PATCH 3/4] Update wfgy-core-reasoning-os.instructions.md --- .../wfgy-core-reasoning-os.instructions.md | 188 +----------------- 1 file changed, 10 insertions(+), 178 deletions(-) diff --git a/instructions/wfgy-core-reasoning-os.instructions.md b/instructions/wfgy-core-reasoning-os.instructions.md index e8e4c74ba..94cbe520d 100644 --- a/instructions/wfgy-core-reasoning-os.instructions.md +++ b/instructions/wfgy-core-reasoning-os.instructions.md @@ -1,91 +1,22 @@ --- -description: 'A plain-text reasoning core (WFGY Core 2.0) system prompt plus a 60-second self-test to make GitHub Copilot more stable on multi-step reasoning tasks.' +description: 'A text-only reasoning core (WFGY Core 2.0) you can drop into GitHub Copilot instructions to make multi-step reasoning more stable.' --- # WFGY Core 2.0 reasoning OS for GitHub Copilot -hi copilot builders, +This file provides a small, text-only reasoning core that you can plug into GitHub Copilot Chat as a custom instruction. +It does not require new tools, agents, or APIs; it only changes how the model organizes its reasoning. -this is meant to be a “drop-in reasoning core” you can hand to GitHub Copilot as a custom instruction. +## How to use -i’m PSBigBig, an indie dev. -before my github repo went over 1.5k stars, i spent one year on a very simple idea: -instead of building yet another tool or agent, -i tried to write a small “reasoning core” in plain text, -so any strong llm (including copilot chat) can use it without new infra. +1. Copy the **Instructions block** below into `.github/copilot-instructions.md` + or into a `*.instructions.md` file under `.github/instructions/`. +2. Reload or open a new Copilot Chat and use it as normal (coding, debugging, planning, etc.). +3. To compare, temporarily remove this block and repeat the same tasks with the same prompts. -i call it **WFGY Core 2.0**. +## Instructions block (WFGY Core 2.0) -this file gives you two things: - -- one system prompt block you can paste as an instruction -- one 60-second self-test so you can feel the difference by yourself - -no signup, no API, no hidden tricks. -just text. - - -## 0. very short version - -what it is: - -- not a new model, not a fine-tune -- one txt block you put in system / instructions -- goal: less random hallucination, more stable multi-step reasoning -- still cheap, no tools, no external calls - -how people use it: - -- some people treat it as a “math bumper” under the model -- advanced users can turn this into a real code benchmark later -- in this instructions file we keep it super beginner-friendly: - just **two prompt blocks you can run inside copilot chat** - - -## 1. how to use with GitHub Copilot (or any strong llm) - -very simple workflow if you want to try this as a **workspace-level copilot instruction**: - -1. copy the “system prompt” block in section 3 -2. put it into `.github/copilot-instructions.md` - - or into a `*.instructions.md` file in `.github/instructions/` -3. open a new Copilot Chat and ask your normal questions - (math, code, debugging, planning, etc.) -4. later you can compare “with core” vs “no core” yourself - -for quick A/B testing, you can also: - -- keep a second project / branch without this instruction -- or temporarily comment this block out and retry the same tasks - -for now, just treat it as a math-based “reasoning bumper” -sitting under Copilot’s usual behavior. - - -## 2. what effect you should expect (rough feeling only) - -this is not a magic on/off switch. - -but in my own tests (across different llms), typical changes look like: - -- answers drift less when you ask follow-up questions -- long explanations keep the structure more consistent -- the model is a bit more willing to say “i am not sure” - instead of inventing fake details -- when you use the model to write prompts for image generation, - the prompts tend to have clearer structure and story, - so many people feel “the pictures look more intentional, less random” - -of course, this depends on your tasks and the base model. -that is why there is also a small **60-second self-test** in section 4. - -if you like numbers, you can turn that test into a fixed benchmark later. -inside this repo, it is ok if you start with “rough feeling only”. - - -## 3. system prompt: WFGY Core 2.0 (paste into system / instructions) - -copy everything in this block into your system / pre-prompt / instructions: +Copy everything in this block into your system / pre-prompt / instructions: ```text WFGY Core Flagship v2.0 (text-only; no tools). Works in any chat. @@ -122,102 +53,3 @@ lambda_observe is: convergent if Delta ≤ −0.02 and E_resonance non-increasin recursive if |Delta| < 0.02 and E_resonance flat; divergent if Delta ∈ (−0.02, +0.04] with oscillation; chaotic if Delta > +0.04 or anchors conflict. [DT micro-rules] -```` - -yes, it looks like math. -it is ok if you do not understand every symbol. -you can still use it as a “drop-in” reasoning core. - -for Copilot, the main idea is: - -* this block does not fight with your existing style guides -* it just gives the model a second, math-like lens -* you can combine it with language/framework-specific instructions - -## 4. 60-second self test (quick A/B/C comparison) - -this part is for people who want to see some structure in the comparison. -it is still very lightweight and can run inside one Copilot Chat session. - -idea: - -* you keep the WFGY Core 2.0 block in system / instructions -* then you paste the following prompt and let the model simulate A/B/C modes -* the model will produce a small table and its own guess of uplift - -this is a self-evaluation, not a scientific paper. -if you want a serious benchmark, you can translate this idea into real code and fixed test sets later. - -here is the test prompt (second block, keep it exactly as-is): - -```text -SYSTEM: -You are evaluating the effect of a mathematical reasoning core called “WFGY Core 2.0”. - -You will compare three modes of yourself: - -A = Baseline - No WFGY core text is loaded. Normal chat, no extra math rules. - -B = Silent Core - Assume the WFGY core text is loaded in system and active in the background, - but the user never calls it by name. You quietly follow its rules while answering. - -C = Explicit Core - Same as B, but you are allowed to slow down, make your reasoning steps explicit, - and consciously follow the core logic when you solve problems. - -Use the SAME small task set for all three modes, across 5 domains: -1) math word problems -2) small coding tasks -3) factual QA with tricky details -4) multi-step planning -5) long-context coherence (summary + follow-up question) - -For each domain: -- design 2–3 short but non-trivial tasks -- imagine how A would answer -- imagine how B would answer -- imagine how C would answer -- give rough scores from 0–100 for: - * Semantic accuracy - * Reasoning quality - * Stability / drift (how consistent across follow-ups) - -Important: -- Be honest even if the uplift is small. -- This is only a quick self-estimate, not a real benchmark. -- If you feel unsure, say so in the comments. - -USER: -Run the test now on the five domains and then output: -1) One table with A/B/C scores per domain. -2) A short bullet list of the biggest differences you noticed. -3) One overall 0–100 “WFGY uplift guess” and 3 lines of rationale. -``` - -usually this takes about one minute to run. -you can repeat it some days later to see if the pattern is stable for you. - -## 5. why this belongs in awesome-copilot - -many builders want stronger reasoning from any llm, -but don’t want to spin up new infra, tools, or agents. - -this is just a text layer. - -* drop-in -* MIT-licensed -* no lock-in -* works side-by-side with your existing language/framework instructions - -if you are curious about the bigger project, it is under: - -* GitHub: `onestardao / WFGY` -* the WFGY 2.0 core is the engine behind that work - -but you do not need to go there to try this. - -this instructions file is meant as a small gift for copilot users: -a way to experiment with a mathematical “reasoning core” -without leaving your editor. From ee9e3bdd30c801bd91c04098a37e46ebdca8f4f1 Mon Sep 17 00:00:00 2001 From: onestardao Date: Thu, 26 Feb 2026 04:47:21 +0000 Subject: [PATCH 4/4] docs: run npm start to update generated files (#719) --- docs/README.instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.instructions.md b/docs/README.instructions.md index 49cb6ece7..611e366c7 100644 --- a/docs/README.instructions.md +++ b/docs/README.instructions.md @@ -191,5 +191,5 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on | [Use Code Components in Power Pages](../instructions/pcf-power-pages.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-power-pages.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-power-pages.instructions.md) | Using code components in Power Pages sites | | [Visual Studio Extension Development with Community.VisualStudio.Toolkit](../instructions/vsixtoolkit.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvsixtoolkit.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvsixtoolkit.instructions.md) | Guidelines for Visual Studio extension (VSIX) development using Community.VisualStudio.Toolkit | | [VueJS 3 Development Instructions](../instructions/vuejs3.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvuejs3.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fvuejs3.instructions.md) | VueJS 3 development standards and best practices with Composition API and TypeScript | -| [WFGY Core 2.0 reasoning OS for GitHub Copilot](../instructions/wfgy-core-reasoning-os.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwfgy-core-reasoning-os.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwfgy-core-reasoning-os.instructions.md) | A plain-text reasoning core (WFGY Core 2.0) system prompt plus a 60-second self-test to make GitHub Copilot more stable on multi-step reasoning tasks. | +| [WFGY Core 2.0 reasoning OS for GitHub Copilot](../instructions/wfgy-core-reasoning-os.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwfgy-core-reasoning-os.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwfgy-core-reasoning-os.instructions.md) | A text-only reasoning core (WFGY Core 2.0) you can drop into GitHub Copilot instructions to make multi-step reasoning more stable. | | [WordPress Development — Copilot Instructions](../instructions/wordpress.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwordpress.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fwordpress.instructions.md) | Coding, security, and testing rules for WordPress plugins and themes |