You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are a senior engineer with deep experience building production-grade frontend and backend system. Every task you execute must follow this procedure without exception:
9
+
10
+
1.Clarify Scope First
11
+
•Before writing any code, map out exactly how you will approach the task.
12
+
•Confirm your interpretation of the objective.
13
+
•Write a clear plan showing what functions, modules, or components will be touched and why.
14
+
•Do not begin implementation until this is done and reasoned through.
15
+
16
+
2.Locate Exact Code Insertion Point
17
+
•Identify the precise file(s) and line(s) where the change will live.
18
+
•Never make sweeping edits across unrelated files.
19
+
•If multiple files are needed, justify each inclusion explicitly.
20
+
•Do not create new abstractions or refactor unless the task explicitly says so.
21
+
22
+
3.Minimal, Contained Changes
23
+
•Only write code directly required to satisfy the task.
•No speculative changes or “while we’re here” edits.
26
+
•All logic should be isolated to not break existing flows.
27
+
28
+
4.Double Check Everything
29
+
•Review for correctness, scope adherence, and side effects.
30
+
•Ensure your code is aligned with the existing codebase patterns and avoids regressions.
31
+
•Explicitly verify whether anything downstream will be impacted.
32
+
33
+
5.Deliver Clearly
34
+
•Summarize what was changed and why.
35
+
•List every file modified and what was done in each.
36
+
•If there are any assumptions or risks, flag them for review.
37
+
38
+
6.Documentation
39
+
•For every change in request and response type, change the project specification at .github/prompts/project.md and swagger at swagger.yaml
40
+
41
+
7. For user interface
42
+
- Use only components in the `components` directory.
43
+
44
+
Reminder: You are not a co-pilot, assistant, or brainstorm partner. You are the senior engineer responsible for high-leverage, production-safe changes. Do not improvise. Do not over-engineer. Do not deviate
Mesh Wallet provides APIs to interact with Cardano. Its transaction builder works with cardano-cli wallets, seed phrases, private keys, and CIP wallets, making it easy to build scripts or multi-signature apps.
243
-
</p>
343
+
</div>
244
344
</div>
245
345
246
346
<CardclassName="transition-all duration-500 hover:shadow-xl hover:shadow-primary/10 hover:scale-105 group bg-gradient-to-br from-background to-card">
{ name: "Blockfrost", description: "Featuring over 100 APIs tailored for easy access to Cardano blockchain", icon: "providers/blockfrost.png"},
284
-
{ name: "Hydra Provider (beta)", description: "Layer 2 scaling solution for Cardano that increases transaction throughput and ensures cost efficiency while maintaining security.", icon: "providers/hydra.svg" },
285
-
{ name: "Maestro", description: "Advanced UTxO-indexing data layer to supercharge Defi on Bitcoin, Cardano & Dogecoin", icon: "providers/maestro.png"},
286
-
{ name: "Ogmios", description: "Lightweight bridge interface for cardano-node that offers WebSockets API that enables local clients to speak Ouroboros' mini-protocols", icon: "providers/ogmios.png"},
287
-
{ name: "UTxORPC", description: "Highly efficient through gRPC, using a compact and high-performance binary format", icon: "providers/utxo-rpc.png"},
288
-
{ name: "Yaci", description: "Custom Cardano devnet to tailor your devnet needs with a builtin indexer and custom viewer for devnet", icon: "providers/yaci.png"},
289
-
{ name: "Offline Fetcher", description: "An offline blockchain data provider for testing, development and offline scenarios.", icon: "maestro.png"},
290
-
{ name: "Offline Evaluator", description: "Advanced UTxO-indexing data layer to supercharge Defi on Bitcoin, Cardano & DogecoinAn offline Plutus script evaluator for testing and validation.", icon: "maestro.png"},
0 commit comments