@aicraftalchemy/aiaca 1.0.11 → 1.0.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli.js +25 -0
- package/package.json +1 -1
package/dist/cli.js
CHANGED
|
@@ -941,6 +941,31 @@ When writing code:
|
|
|
941
941
|
- Create complete implementations, not stubs
|
|
942
942
|
</code_quality>
|
|
943
943
|
|
|
944
|
+
<coding_excellence>
|
|
945
|
+
This is how elite engineers work \u2014 apply it to every coding task so output competes with the best.
|
|
946
|
+
|
|
947
|
+
1. UNDERSTAND BEFORE WRITING. Read the surrounding code, existing patterns, types, and conventions
|
|
948
|
+
first. Solve the real underlying problem, not just the literal surface request. Know the inputs,
|
|
949
|
+
outputs, constraints, and how this fits the wider system before you touch a line.
|
|
950
|
+
2. REASON ABOUT CORRECTNESS. Identify the invariants and the full set of edge cases (empty, null,
|
|
951
|
+
zero, negative, boundary, large input, unicode, concurrency, partial failure) and write code that
|
|
952
|
+
provably handles them. Prefer total functions and explicit error paths over hidden assumptions.
|
|
953
|
+
3. SIMPLICITY OVER CLEVERNESS. Choose the smallest correct design that fits the codebase. No
|
|
954
|
+
speculative abstraction, no premature generalization, no dead options "just in case." Clear beats
|
|
955
|
+
clever. Delete more than you add when you can.
|
|
956
|
+
4. SECURITY & PERFORMANCE BY DEFAULT. No injection-prone string building, validate inputs at trust
|
|
957
|
+
boundaries, never hardcode secrets. Avoid N+1 and accidental O(n^2); pick the right data structure
|
|
958
|
+
and algorithm the first time. These are defaults, not afterthoughts.
|
|
959
|
+
5. SELF-REVIEW BEFORE DONE. Re-read your own diff as a harsh critic: hunt for bugs, off-by-ones,
|
|
960
|
+
unhandled cases, broken imports, and inconsistencies with the codebase. Assume it is wrong and
|
|
961
|
+
find why. Then run the build and tests to confirm reality matches intent.
|
|
962
|
+
6. LEAVE IT BETTER. Match the project's style exactly, name things precisely, keep functions focused,
|
|
963
|
+
and make the change cohesive \u2014 as if the original authors wrote it.
|
|
964
|
+
|
|
965
|
+
Mediocre, almost-working, or "good enough" code is a failure. Ship code you would stake your
|
|
966
|
+
reputation on.
|
|
967
|
+
</coding_excellence>
|
|
968
|
+
|
|
944
969
|
<error_recovery>
|
|
945
970
|
When something fails:
|
|
946
971
|
- Read the error message carefully
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aicraftalchemy/aiaca",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.12",
|
|
4
4
|
"description": "AIACA — AI Agentic Coding Assistant. A production-grade agentic CLI with dual-provider support (Gemini + Claude), rich TUI, and 100+ tools.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|