<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>workflow on philliant</title><link>https://philliant.com/tags/workflow/</link><description>Recent content in workflow on philliant</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 philip mathew hern</copyright><lastBuildDate>Thu, 26 Mar 2026 06:31:57 -0700</lastBuildDate><atom:link href="https://philliant.com/tags/workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>the danger of trusting the ai agent</title><link>https://philliant.com/posts/20260326-the-danger-of-trusting-the-ai-agent/</link><pubDate>Thu, 26 Mar 2026 06:31:57 -0700</pubDate><guid>https://philliant.com/posts/20260326-the-danger-of-trusting-the-ai-agent/</guid><description>i share a real failure mode where an ai agent created and then deleted files while debugging, leaving a clean git tree but low confidence. the lesson for me is simple: ai should accelerate the work i own and understand, while domain-specific decisions stay with the people accountable for that domain.</description></item><item><title>deep dive: the ai models i use</title><link>https://philliant.com/posts/20260320-deep-dive-ai-models-i-use/</link><pubDate>Fri, 20 Mar 2026 10:45:00 -0700</pubDate><guid>https://philliant.com/posts/20260320-deep-dive-ai-models-i-use/</guid><description>i walk through composer-2, gpt-5.3-codex-xhigh, claude 4.6 opus, gemini 3.1 pro, grok-4-20, and kimi-k2.5 with a comparison table plus longer notes on how i actually use each one.</description></item><item><title>a practical ai workflow: jira, github, and mcp</title><link>https://philliant.com/posts/20260319-practical-ai-workflow-jira-github-mcp/</link><pubDate>Thu, 19 Mar 2026 11:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260319-practical-ai-workflow-jira-github-mcp/</guid><description>i connect my editor to jira and github through mcp, create well-structured issues from templates before coding, and reuse that text in pull requests so every agent in the chain has the same ground truth.</description></item><item><title>starter templates for ai rules, skills, and commands</title><link>https://philliant.com/posts/20260315-starter-templates-for-ai-rules-skills-and-commands/</link><pubDate>Sun, 15 Mar 2026 04:00:00 -0700</pubDate><guid>https://philliant.com/posts/20260315-starter-templates-for-ai-rules-skills-and-commands/</guid><description>this follow-up post gives practical, generic templates you can adapt for rules, skills, and commands, plus side-by-side examples that show why tighter structure improves ai execution quality.</description></item><item><title>how to use ai to create ai rules, skills, and commands</title><link>https://philliant.com/posts/20260314-how-to-use-ai-to-create-ai-rules-skills-and-commands/</link><pubDate>Sat, 14 Mar 2026 11:15:00 -0700</pubDate><guid>https://philliant.com/posts/20260314-how-to-use-ai-to-create-ai-rules-skills-and-commands/</guid><description>this kickoff post explains why ai-authored rule, skill, and command scaffolds are often clearer for ai execution, and how to keep humans in control with constraints, reviews, and acceptance checks.</description></item><item><title>ai br-ai-n fr-ai</title><link>https://philliant.com/posts/20260314-ai-br-ai-n-fr-ai/</link><pubDate>Sat, 14 Mar 2026 10:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260314-ai-br-ai-n-fr-ai/</guid><description>this post frames ai brain fry as a workflow design problem and gives a practical framework to reduce cognitive overload while keeping ai leverage high.</description></item><item><title>my cursor setup</title><link>https://philliant.com/posts/20260313-my-cursor-setup/</link><pubDate>Fri, 13 Mar 2026 10:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260313-my-cursor-setup/</guid><description>this is my real cursor setup as of march 13, 2026, rewritten as a practical tutorial with settings explanations, mcp server breakdowns, and a replication checklist.</description></item></channel></rss>