Introducing Claude Tag, a new way for teams to work with Claude.
In Slack, Claude joins as a team member with access to the channels and tools you choose. Tag Claude in and delegate tasks to it while you focus on other work.
6/18-19、韓国 ソウルにて行われるグローバルスタートアップフェア「NextRise 2026」にArchiXが出展いたします。
韓国語も対応している建築特化のAIを、ソウルの会場でぜひご体験ください!
6/18~19, 대한민국 서울에서 개최되는 글로벌 스타트업 페어 'NextRise 2026'에 ArchiX가 참가합니다.
한국어 지원이 가능한 건축 특화 AI를 서울 행사장에서 꼭 체험해 보세요. 여러분의 많은 관심과 방문을 부탁드립니다!
https://t.co/Zg3UPGryb1
Met one of my mentors for lunch today.
Whenever we meet, theres one question I ask him all the time.
“What’s your image of a good engineer?”
His thoughts:
Although this has been true from the very start, but just very obvious right now.
A good engineer understands the business goals and uses their expertise to reach them in the simplest way possible:
through smart architectural decisions, leveraging the team, cutting the BS.
To get those qualities, either you have to wait for your YOE to go up.
OR
Create it yourself - through ACTION.
i.e create loads of internal tools, take on challenging tasks that force you to grow.
Doing the above also makes you a trustworthy employee. And trust attracts opportunities. See how that connects?
A close friend of mine set out a chuckle when I was happy that a certain tool we were going to use had their own skill files.
Turns out I gotta sprinkle some of my thoughts on why I am bullish on skill files:
1. Instructing best practices to agents
2. People see varied output with the same agents cuz of their thought process/prompts - skill files helps to make sure theres no fuck-ups for clearly defined things.
3. If someone does something really nicely with agents in a team. Make it a skill and pass it to others. Reduces unnecessary slop.