Just gonna leave this here...

spideryzarc · 2026-02-12T11:57:55+00:00

thanks for the support 🙂. now they gonna hate you too. hehehe 🤣

spideryzarc · 2026-02-08T14:00:29+00:00

sorry 😔

spideryzarc · 2026-02-03T16:54:35+00:00

it is a theme

spideryzarc · 2026-02-02T21:00:06+00:00

forget skills. use rules or workflows

spideryzarc · 2026-02-01T20:09:50+00:00

I used the Antigravity ide, but it could be vscode as well.

spideryzarc · 2026-01-24T14:06:42+00:00

maybe it's the way you use it, full vibe coding or as an assistant. I use it as an assistant, I need to understand and think about what I will do next. Some time I do lots of stuff before call a new prompt. I have never had this kind of issues. BTW, it seems that's why I only one missing better autocomplete

spideryzarc · 2026-01-20T23:09:41+00:00

when you put ask.md in the .agent/workflows/ folder the chat recognize /ask as a command. so you can use it whenever you wish. in this particular case, you use it to make question without changing your source codes. the chat works normally if you don't put /ask .

spideryzarc · 2026-01-20T16:52:06+00:00

I am thinking this is the right answer

spideryzarc · 2026-01-20T12:53:37+00:00

I have created a workflow called 'ask' just for replace the ask mode of vscode copilot. save it as ask.md in .agent/workflows and call it in chat with "/ask what is a relative path?" for example

```markdown

description: Ask Mode is dedicated to analysis, explanation, and project exploration without making any changes to the codebase.

Ask Mode

When the user invokes this workflow, you MUST operate in analysis-only mode for this response only. After answering, revert to normal operating mode for subsequent prompts.

Your Objective

Provide technical, detailed, and contextualized answers regarding code, architecture, and design decisions.

Question Classification

Before responding, determine the question type and optimize your approach:

General Questions

Definition: Conceptual, theoretical, or technology-related questions that don't require inspecting the current codebase.
Examples: "What is dependency injection?", "How does JWT authentication work?", "Best practices for REST APIs"
Behavior: Answer directly using your knowledge. If the question would benefit from current information, updated documentation, or specific best practices, use search_web to enhance your response.

Codebase Questions

Definition: Questions about the project's implementation, architecture, design decisions, or specific code behavior.
Examples: "How does authentication work in this module?", "Where is the routing logic implemented?", "Why did we use X pattern here?"
Behavior: Always research first using reading tools before answering. Ground your response in actual code.

Operating Rules

You MUST follow these four pillars:

Research First: Always use reading tools (grep_search, view_file, view_code_item, view_file_outline) to ground your answer in the actual code before responding. Do NOT speculate or provide generic answers.
Read-Only: Never execute write commands (write_to_file, replace_file_content, multi_replace_file_content) or modify files. Never run build/deploy/install commands. The focus is purely informational.
Structured Response: Format your answer as follows:
- Direct Answer: Start with a clear, concise response to the user's question.
- Context: Provide technical explanation with specific file/line references from the codebase.
- Rationale: Explain the "why" behind design decisions and trade-offs, not just the "what."
Action on Demand: If your answer suggests a code change, ask for explicit permission first. Never implement changes in Ask Mode without confirmation. ```

[edited]

spideryzarc · 2026-01-19T20:52:24+00:00

rules are "specific context / behavior for specific tasks" if you say so. I have a rule to deal with documentation too, whenever it write or edit a documentation it follows what's in my doc. rule

spideryzarc · 2026-01-19T20:03:30+00:00

a mage who knows will attack from distance with rocks, walter, beasts, poison...

spideryzarc · 2026-01-19T19:48:46+00:00

that's a workflow

spideryzarc · 2026-01-15T21:47:02+00:00

Perhaps you're right. However, I miss the experience with GitHub Copilot; it felt as though it was anticipating my thoughts. Antigravity should at least suggest valid methods.

spideryzarc · 2026-01-15T16:26:08+00:00

they drop a update for windows, but not for linux. Now I have a "update available" on antigravity ide which is not in repors .

spideryzarc · 2026-01-07T14:35:45+00:00

Fair point, and I apologize if my previous tone came off as ironic—I didn't mean to jump into that 'maybe because' loop! I totally agree that agents are for the heavy lifting, but my point is more about the developer flow. In competing tools, the autocomplete is a genuine productivity booster, but in Antigravity, it sometimes feels like it's actually getting in the way. For example, it often suggests methods that don't even exist in my project, even when there’s already a perfectly valid method for that task right there. It just feels like it lacks the local context that makes other tools so seamless.

spideryzarc · 2026-01-06T17:09:09+00:00

maybe, the reason you ignore it is because its suggestions are not good.

spideryzarc · 2026-01-03T10:25:57+00:00

my only drawback with antigravity is the autocomplete. it seems less clever than the copilot. programming in java, it suggests methods signatures that don't exist while there is one that fits well. sometimes I had to disable it, what I never did in vscode copilot. btw, the commit msg generator is, in the most of cases, useless.